Many Sessions Waiting For Update DML On SNP_SB Table From ODI 12.2.1 Agent Without Executing Which is Saturating The Repository Database Sessions
(Doc ID 2241367.1)
Last updated on MAY 12, 2017
Applies to:Oracle Data Integrator - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
In ODI 12.2.1 agent side, it is observed that many sessions wait for update DML on Work Repository SNP_SB table and it saturates the Repository database Sessions. The sample DML query looks like below:
SESS1.SB_NO FROM (SELECT DISTINCT SESS.SB_NO FROM SNP_SESSION SESS JOIN
SNP_SB SB ON SESS.SB_NO = SB.SB_NO AND SESS.SESS_MESS='8b316ddd-d84e-44d7-
ac98-4307f708b978' LEFT JOIN SNP_SCEN SCEN ON SB.SCEN_NO = SCEN.SCEN_NO AND
SB.SCEN_SNAPSHOT_NO = SCEN.SCEN_SNAPSHOT_NO WHERE SCEN.SCEN_NO IS
NULL) SESS1 LEFT JOIN (SELECT DISTINCT SB_NO FROM SNP_SESSION WHERE
SESS_MESS IS NULL) SESS2 ON SESS1.SB_NO = SESS2.SB_NO WHERE SESS2.SB_NO IS NULL)
This query is initiated by the agent automatically and it is not from actual job execution. The select inside the update DML seems to be the main cause of the issue.
Is it possible to create indexes on the table SNP_SESSION and SNP_SCEN to improve the performance at execution time?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document