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

    Voyager Global Data Change job does not change status from Kill to Killed

    • Product: Voyager
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Question

    I had to kill a Global Data Change job by clicking the "Kill Job" button, and its status is not changing from "Kill" to "Killed" as per the "Kill Job" section in the Global Data Change User's Guide.  As a result the "Delete Job" button is grayed out and new GDC jobs that are submitted don't run.

    Answer

    If you click the "Kill Job" button in Global Data Change, its status should change to "Kill".  The system should then when it is safe to do so gracefully close any open processes for the job and change its status to "Killed".  At that point the job can be deleted via the "Delete Job" button.

    If the job status does not change from "Kill" to "Killed" within fifteen minutes or so, contact Voyager Support.

    Additional Information

    Every job that displays in the GDC Job Management > View Running/Completed screens will appear in the JOB_DATA table.  This table is part of GDC's rule management functionality.  The JOB_STATUS table describes the status codes used in JOB_DATA: 0=pending, 1=running, 2=done, 3=kill, 4=killed, 5=failed.

     


    • Article last edited: 06-Feb-2021