How To Avoid Blocked Database Sessions Running 'UPDATE SNP_SESSION SET NB_CHILD_RUN=NB_CHILD_RUN - 1 WHERE SESS_NO=:1' When Using The ODI OdiPurgeLog Tool
(Doc ID 1993320.1)
Last updated on MARCH 10, 2017
Oracle Data Integrator - Version 10.1.3.2.0 and later
Information in this document applies to any platform.
The following Oracle Data Integrator (ODI) command is issued for deleting the log:
OdiPurgeLog "-PURGE_TYPE=ALL" "-TODATE=#UTILITIES.ODI_LOGPURGEDATE" "-STATUS=D" "-PURGE_REPORTS=YES" "-XML_CHARSET=ISO-8859-1" "-JAVA_CHARSET=ISO8859_1" "-REMOVE_TEMPORARY_OBJECTS=YES"
with the ODI_LOGPURGEDATE Variable refreshed as follows:
select to_char(SYSDATE,'YYYY-MM-DD')||' ' ||'18:00:00' from dual
This job may not purge all the logs, and result in database sessions that are stuck / blocked while running the following SQL command:
UPDATE SNP_SESSION SET NB_CHILD_RUN=NB_CHILD_RUN - 1 WHERE SESS_NO=:1
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 hundreds of Community platforms