Cleaning Up After an Early Exit - Cleaning Up After an Early Exit - Perceptive Content - Perceptive Content Database Upgrade Package for SQL Server - Perceptive-Content/Perceptive-Content-Database-Upgrade-Package-for-SQL-Server/Foundation-26.1/Perceptive-Content-Database-Upgrade-Package-for-SQL-Server-Reference-Guide/Cleaning-Up-After-an-Early-Exit - Foundation 26.1 - Foundation 26.1

Perceptive Content Database Upgrade Package for SQL Server Reference Guide

Platform
Perceptive Content
Product
Perceptive Content Database Upgrade Package for SQL Server
Release
Foundation 26.1
License
ft:lastPublication
2026-04-16T22:28:17.811000
ft:locale
en-US

You can use the following procedures to release the application resource locks for the procedures and identifiers or to manually clear the call stack and session attribute tables 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 inuser.IN_DB_UTIL_SP_CLEAR_IDENTIFIER 'ALL'; 
  • Clear session and call stack for only the SYNC identifier
    EXEC inuser.IN_DB_UTIL_SP_CLEAR_IDENTIFIER 'SYNC'; 
  • Clear session and call stack for only the UPGRADE identifier
    EXEC inuser.IN_DB_UTIL_SP_CLEAR_IDENTIFIER 'UPGRADE';