Siebel Audit Trails select from S_AUDIT_ITEM table causing blocking sessions on the database (Doc ID 1589125.1)

Last updated on APRIL 03, 2025

Applies to:

Symptoms

SIEBEL VERSION:
---------------
Siebel 8.1.1.6

ISSUE STATEMENT:
----------------

Customer has some integrations running on Siebel application. During the integration transactions, it was observed that a specific type of SQL statement was issued against the database, where the SQL statement appears to be blocking sessions in the Database.

The customer's DBA identified the SQL which is creating the blocking contentions, but even after killing the blocking session, it is creating another blocking session on the same SQL afterwards.

The SQL in question is the following:

UPDATE SIEBEL.S_ASSET SET MODIFICATION_NUM = MODIFICATION_NUM + 1, LAST_UPD = :B4, LAST_UPD_BY = :B3, DB_LAST_UPD_SRC = :B2, DB_LAST_UPD = CURRENT_DATE, DLR_ID = :B1 WHERE ROW_ID IN (SELECT TBL_RECORD_ID FROM SIEBEL.S_AUDIT_ITEM WHERE GROUP_NUM = :B5)

NAME POSITION DATATYPE_STRING VALUE_STRING
------------------------------ ---------- --------------- --------------------
:B4 1 VARCHAR2(32)
:B4 1 VARCHAR2(32)
:B3 2 VARCHAR2(32)
:B3 2 VARCHAR2(32)
:B2 3 VARCHAR2(128)
:B2 3 VARCHAR2(128)
:B1 4 VARCHAR2(32)
:B1 4 VARCHAR2(32)
:B5 5 VARCHAR2(32) 1-12I4IO5
:B5 5 VARCHAR2(32) 1-12I4IO5

ERROR MESSAGE:
-------------------
There are no error messages that occurs with this issue, rather the SQL is blocking other sessions/connections to the database.

Cause

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