Skip to main content
ExLibris

  • Subscribe by RSS
    • Aleph
    Ex Libris Knowledge Center

    aleph_startup fails to start batch queues and daemons for certain libraries

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Description:
    aleph_startup starts the batch que's, indexing daemons, request daemons, etc., for some libraries, but fails to start them for others.

    The queues and daemons for these libraries *can* be started successfully using util c/1 and the util e menu.

    Resolution:
    Which libraries have their que's and daemons started is determined by the QUE_STARTUP_LIBS, WORD_STARTUP_LIBS, etc., setenv's in aleph_start.private. You need to add these libraries to these lists.
    After making a change to aleph_start.private, you need to do
    > source aleph_start
    to make it take effect.

     

    Additional Information:  

    In another case, the batch queues didn't start because Oracle went down during the run of aleph_startup.  From the aleph_startup.log:

    Oracle error: handle_connection 
    ORA-01089: immediate shutdown in progress - no operations are permitted 

    In this case, the solution is to run aleph_shutdown / aleph_startup after Oracle is back up.

     

     

    • Article last edited: 29-Mar-2017
    //Feedback