Cleanup After an Early Exit - Perceptive Content Database IN_DB_UTIL Package for Oracle Server - Foundation 24.1 - Foundation 24.1 - Ready - Perceptive Content - external

You can use the IN_SESSION_CLEAR and IN_SESSION_CLEAR_ALL procedures to manually clear the call stack and session attributes as needed due to an unhandled exception or after manually cancelling an operation before completion.

Important Do not execute any of the following commands if any operations are still in progress as it will clear the call-stack and session attributes which will lead to undesired results and unhandled exceptions.

• Clear session and call stack for all identifiers (SYNC and UPGRADE).

  EXEC IN_DB_UTIL.IN_SESSION_CLEAR_ALL('ALL');

• Clear session and call stack for only the SYNC identifier EXEC

   IN_DB_UTIL.IN_SESSION_CLEAR_ALL ('SYNC');

• Clear session and call stack for only the UPGRADE identifier

  EXEC IN_DB_UTIL.IN_SESSION_CLEAR_ALL ('UPGRADE');

• Clear session and call stack for only the IN_DB_UTIL identifier

  EXEC IN_DB_UTIL.IN_SESSION_CLEAR_ALL ('IN_DB_UTIL');