- Article Type: General
- Product: Aleph
- Product Version: 20
util c/3 doesn't stop batch queue. There are two cases:
1) you see the message "batch que wasn't killed yet; wait for termination?" or
2) there is no message, the util process is exited, but util c/1 shows that the batch queue has not stopped.
Case 1) The "batch que wasn't killed yet; wait for termination?" occurs when there is a job started by the batch queue (with the lib_batch process as its parent) which is still running.
If you respond with "Y", it will keep repeating the "batch que wasn't killed yet; wait for termination ?" message until all the jobs with lib_batch as their parent are completed.
If you respond with "N", it sets the "d_lib_b_status = killed" flag and exits the util. After the jobs with lib_batch as their parent are done, it terminates the lib_batch process.
Case 2) We know of two causes for this:
a) not stopping the batch queue when you stop Oracle (for doing a backup); and
b) starting aleph as root. (If this is the cause, df1 -> "ls -lrt" will show "root" as the owner of the que_batch file.)
In either case, you will need to take the process number (nnnn) you see in util c/1 (the first number) for the lib_batch process and do "kill -9 nnnn" to kill the process.
See Article 000045870 for complete info on deletion of the batch queue ( Services-submitted jobs don't run; batch queue doesn't work **MASTER RECORD** ).
See Article 000046887 in regard to the general handling of the aleph-started-as-root condition ( Repeated utf_files errors for the same file(s); "Not owner" for "kill" command ).
Category: Background processing
- Article last edited: 11/20/2014