Skip to main content
ExLibris

Knowledge Assistant

BETA
Voyager

 

Ex Libris Knowledge Center
  1. Search site
    Go back to previous article
    1. Sign in
      • Sign in
      • Forgot password
  1. Home
  2. Voyager
  3. Knowledge Articles
  4. Jobs in GDC queue never start

Jobs in GDC queue never start

  1. Last updated
  2. Save as PDF
  3. Share
    1. Share
    2. Tweet
    3. Share
  1. Problem Symptoms
  2. Cause
  3. Resolution
  4. Additional Information
  • Product: Voyager
  • Product Version: 8.0.0
  • Relevant for Installation Type: Dedicated-Direct; Direct; Local

Problem Symptoms

Jobs in Global Data Change Job Queue are never started - jobs just sit in the queue

GDC jobs with a start time of "now" should usually start within a few minutes.  There is a job scheduler function that checks the queue regularly, and typically a job that was submitted should start within 5 minutes or less.  Note however that only one job at a time will run, so new jobs queue up behind a running job. In some situations jobs can get "stuck" and additional jobs will not run (an example of this is when an operator attempts to KILL a job but it does not transition to KILLED status).  Contact Support if you suspect you may have a problem like this.

Cause

jobd isn't running on the server for the Voyager database instance (xxxdb).

Resolution

  1. Connect to server via SSH or Telnet.
  2. ps -ef | grep jobd
  3. If there is no process for xxxdb listed, start the process:
    1. cd /m1/voyager/xxxdb/sbin
    2. ./Pjobd
  4. Check that process is running for xxxdb: ps -ef | grep jobd | grep xxxdb

Additional Information

If step 3.b. results in "Jobd is running on xxxdb. Please kill PID {PID} and restart the Pjobd program"

  1. Check for the referenced process: ps -ef | grep {PID}     [where {PID} is the PID in the message]. If a process with that PID is not running, continue.
  2. cat /m1/voyager/xxxdb/log/jobd.pid
  3. If the jobd.pid contains the PID from the message, then remove the jobd.pid file: rm -i jobd.pid
  4. Start jobd: /m1/voyager/xxxdb/sbin/Pjobd

If the process does not start, does not remain running after it's started, or Voyager server access is not available (Voyager TotalCare customers, for example), please open a Case with Support.


Article last edited: 10-Mar-2016

 

View article in the Exlibris Knowledge Center
  1. Back to top
    • jobd dies and Scan Job killed when over certain number of Scan Rule Sets in Scan Rule Set Group
    • KEY: errno 22 Reattaching shared memory
  • Was this article helpful?

Recommended articles

  1. Language
    English
    Product
    Voyager
  2. Tags
    1. Global data change (GDC)
  1. © Copyright 2025 Ex Libris Knowledge Center
  2. Powered by CXone Expert ®
  • Term of Use
  • Privacy Policy
  • Contact Us
2025 Ex Libris. All rights reserved