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

    p_manage_32 job ran 14 hours later than we requested; job start and end times

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

    Description:
    Manage_32 was scheduled for Fr 03/07 23pm but according to the log abc01_p_manage_32.11008 it started to run only on Mar 8 07:51(till 13:37), why?

    -rw-rw-r-- 1 aleph aleph 22049 Mar 8 05:35 server_start.log_6604
    -rw-rw-r-- 1 aleph aleph 403017 Mar 8 07:51 abc01_p_manage_15.11010
    -rw-rw-r-- 1 aleph aleph 2143632 Mar 8 13:37 abc01_p_manage_32.11008

    Resolution:
    The date/time which you see in the $alephe_scratch log for a job is *not* the time that the job started; it is the time that the log was last written to. In this case, the abc01_p_manage_32.11008 *finished* at Mar 8 13:37.

    To see when a job began, you need to check the beginning of the job log....

    We see that abc01_p_manage_15.11010 finished at Mar 8 07:51. My guess is that it was running at Fr 03/07 23pm when you intended for the p_manage_32 to start and the latter job waited until the former was finished.

    If the p_manage_15 log shows a start time after 23:00, then you should check the $alephe_scratch logs for other abc01 jobs running in this timeframe.

    In regard to the long run time for p_manage_15:

    * p_manage_15 will take at least 8.5 hours at your site when run against all heading types.

    * When run against just one particular heading type, it should be shorter, but the job was set-up to run against all headings anyway. As described in KB 16384-1969, v18 rpc-1281 corrects this problem, greatly shortening the run-time when the job is run for one specific Type of Heading Index.


    • Article last edited: 10/8/2013