Siebel Unleashed

Let’s jump on to the first performance issue then

Problem Statement:

Drill down from Activities home screen to My Activities view was taking very long time but drill down to All activities was working fine.

Solution Approach:

So, after going through the routine steps to generate log mentioned in first post I moved on to analysis part.

• I spooled both SQL queries (generated from My Activity and All Activity drill down)
• Comparing both SQL queries showed me that number of columns selected were same which meant a particular column was not the cause of problem.
• Then I moved on to the where clause part.
  There was one extra condition in My Activities SQL which was as following
  
T20.CREATED >= TO_DATE (:2, 'MM/DD/YYYY HH24:MI:SS')
and the bind variable had value '01/01/1980 08:00:00'

• I was not able to find place where this search spec had been specified. So, I anlaysed detailed logs.
• After going through logs throughly I noticed that just above the SQL statement a Named Search was being set and it read something like
  
[Set Named Search]
Sort Search Optimization = CREATED >= ‘01/01/1980 08:00:00′

I searched in Bookshelf with term ‘Sort Search Optimization’ and found out that it is user property. Here is excerpt of the text given in bookshelf

“It is an An optimization that helps some databases (mostly Oracle) choose the correct index”
(Not very helpful is it)

I went to next resource available Metalink and search for the term and this what I found out in one of the SR’s.

“Since the mentioned field user property does not always determine whether it is used or not and the Sort Search Optimization is determined at run time by the Siebel Object Manager and we can not control it “

To read complete SR click here

Was this is a dead end?
Was I able to find something ?

Well, next post will provide you anwsers of the above questions when I will discuss details of the Sort Search Optimization user property in detail. Stay tuned till then