Applies to:Product Release: V7 (Enterprise)
Version: 7.5.3  Fin Svcs
Database: IBM DB2/UDB 7.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-2417475547.
We are facing a performance issue when we delete records from 'UHCKA Influencer' business
component. The delete takes around 45 seconds to 1 minute. We did take a spool and found out that
the longest running queries are a set of insert statments into SIEBELP.S_DOCK_TXN_SET. Is there
any way in which we can improve the performance of Delete on this business
Note: UHCKA Influencer is a copy of contact business component.
We are enclosing the sif of UHCKA Influencer and the spool file for you reference
This is a known issue in Siebel version 7.5.3, when you commit the first delete of a record in the Siebel application using the Siebel Web Client, you may experience a delay in the application before the control is returned to you.
Change Requests 12-HJQX15 and 12-IJU4NB has been raised to address this product defect.
The reason for this behavior is that the Siebel Object Manager needs to read all the link definitions and business component definitions related to the links for the whole repository to find the links that are related to the active business component. This is performed by the Siebel Object Manager the first time a commit is issued for a delete statement. Due to the number of links in the Siebel repository that need to be read, this may take a long time.
The above behavior happens only for the very first delete issued through the Object Manager. Subsequent deletes should complete more quickly for the same business component or different business Components.
Maintenance Release Request 12-IJU4QY has been released for Change Requests 12-HJQX15 and 12-IJU4NB, which has been fixed in Siebel Fix Pack version 18.104.22.168. The latest Fix Pack should be applied to Siebel Maintenance Release 7.5.3.