Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Library batch queue shut down after job failed. Is this normal?

    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    util c/1 doesn't show any lib_batch process; but when we try to start it with util c/2, it doesn't start.

    The log of the last batch job which ran had these messages:

    20111024 2015: executing /exlibris/aleph/a20_1/aleph/proc/p_file_04 with parameters ABC50,z108,replace,DLM,
    20111024 2015: log file is: /exlibris/aleph/u20_1/alephe/scratch/mit50_p_file_04.80696
    20111024 2015: job /exlibris/aleph/a20_1/aleph/proc/p_file_04 failed !!!, reentered to que
    20111024 2015: stopping the que
    20111024 2015: ************************************************
    20111024 2015: Batch que ABC50 stopped

    The lib_batch.c program prevents lib_batch from starting following such a failure (in case a subsequent job is dependent on the success of this first job).

    Do util c/8. If the failed job appears there (because it has been "reentered" to the queue) and if you just want to let the other jobs run, you can delete the failed job by specifying its entry number in util c/8. Then util c/1 should start the lib_batch OK. If the failed job doesn't appear in util c/8 or if deleting it doesn't help, consult KB 16384-22097.

    • Article last edited: 10/8/2013