SADMIN CREDENTIALS REVEALED !

Welcome to the wild world of Siebel !!! I got bored coding business logic and wrote a small different script. Look at what it does (Screenshot).

And what does all these mean.

Here's the explanation.

1) All credentials including those for SADMIN and SIEBEL can be easily thrown out in Siebel Output Property Set.

2) I wrote a Runtime-Business Service on thin client to achieve this functionality that can be easily plugged in and out. Also the code has been reliably tested across multiple environments and on different versions (Versions 8.0 and 8.1).

3) There are other cooler ways (zero footprint I mean !!! )

You can contact me thru twitter: (@geeksajan: http://twitter.com/geeksajan)

DISCLAIMER

There are no code or methodologies published in this posting.

This post is a security advisory and should be treated as a responsible disclosure.

SIEBEL ORACLE DRIVER: CAUGHT IN THE ACT

Recently I came across a very peculiar problem in the wild world of Siebel:

There was a PDQ when fired took around 100 secs + to return the result set on the UI.
I was able to trap the killer SQL (SQL Execution Time: 98 secs)
But the same SQL fired directly on the DB took only 2 secs.

The culprit was caught red handed.

The Siebel Oracle driver sscdo90.dll (Sqlstyle : CBO) tunes off the HASH JOIN(with optimizer MODE set to FIRST_ROWS_10) for the session and then fires the query.
Since HASH JOIN is disabled, the performance of this specific query is heavily impacted.

Most popular Interview Question

I am sure you might have heard this in 1st round



How will you edit the joined field values in join?

My First Post

This is my first post on my blog Siebel Musings !