My Oracle Support Banner

Deletion from the S_CONTACT_XM std. 1:M extension table causes 5sec. DELAY AND attempt to DELETE records from the S_ASSET_CON std. intersection table (Doc ID 2087452.1)

Last updated on FEBRUARY 02, 2022

Applies to:

Siebel CRM - Version 7.5.3 [16131] and later
Information in this document applies to any platform.


A Business Component defined on the S_CONTACT_XM table (which is the standard 1:M extension table for "Contact" Business Entiy with root Business Component based on tables: "S_PARTY, S_CONTACT" ...

ISSUE:  Unnecessary Application Performance degradation.
Deletion a record from the of a BC component takes unexpectedly long time (about 5 seconds and more!)

Detaled traces indicates that the time was spend by Siebel Application before executing any SQL-satement

Also the EXTRA DELETE statement  is generated to delete records from the S_ASSET_CON (table, which is standard intersection table for relation the "Asset" and "Contact" Business Entities

 using condition that may never hit any record there: S_ASSET_CON.CONTACT_ID = S_CONTACT_XM.ROW_ID 

(no records in the intersection table may have Contact Id = Row id of a record in the 1:Many Contact extension table).

Sample log snippet that traces at attempt to delete a record from the S_CONTACT_XM  wit Contact_Id = 0-1, Type =EXT_AGG, Name = AGG_1is below:


NOTE: The 5seconds+ DELAY issue was also detected when using a Business Component based in the S_ORG_EXT_XM, which is standard 1-to-many extension table for the "Account" Business Entity ("Account" BC with base tables: S_PARTY. S_ORG_EXT, ...)


No delay occurs. No attempt to delete never existing records from the S_ASSET_CON table is performed.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.