Auto Events Purge Job fails after SCSP server is rebooted
Last Updated September 23, 2014
The Auto Events Purge job fails to run in SCSP, when the customer runs the job manually it runs fine without error. Customer has also tried to reboot the server(s)
Job Failed to run
The SCSP and the DB server were restarted in the wrong event chain, this can lead to the ##SYS and ##DBS temporary tables to not be deleted from the SQL server.
On the SQL server machine, examine System databases -> tempdb -> temporary tables and confirm if ##SYS and ##DBS tables are there. These 2 temporary tables should only exist while the database cleanup thread is running the relevant store procedures. They should be gone once the store procedures are completed.
Examine sis-server.0.log on the SCSP server machine and confirm that the cleanup thread actually started running once an hour after last SCSP server service start-up. But it throws an error each time it runs due to ##SYS table already existing.
Please take the following steps to get rid of ##SYS and ##DBS tables 1. Stop SCSP server service 2. Run “drop table ##SYS” and “drop table ##DBS” in SQL server management studio 3. Start SCSP server service again
After the above steps in sis-server.0.log “performing database cleanup…” message should be logged shortly after the service start-up and no more error messages.
SCSP v5.2.9 MP4
Imported Document ID: TECH217310
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe