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

    How to find out whether Voyager Global Data Change (GDC) is running

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



    How can I tell if Global Data Change (GDC) is running?


    As the root or voyager user run this command:

    ps -efw |egrep -i "gdc|jobd"

    ( Note: -w option prevents ps -ef from truncating output to the width of the terminal window, which may prevent grep from correctly spotting the server processes.) 

    If you just see something like this:

    root     19995 19906  0 10:06 pts/0    00:00:00 egrep -i gdc|jobd

    GDC is not running.


    This is an example of what you might see if GDC is running:

    [VGER] voyager@aio0009 : voyager/ $ ps -efw |egrep -i "gdc|jobd"
    voyager   3663     1  0 01:02 ?        00:00:35 java -Dlog4j.configuration=file:///m1/voyager/xxxdb/ini/ -Xms32m -Xmx64m -Dfile.encoding=UTF-8 -classpath .:/m1/voyager/l
    voyager   3734     1  0 01:02 ?        00:00:37 java -Dlog4j.configuration=file:///m1/voyager/xxxdb/ini/ -Xms32m -Xmx64m -Dfile.encoding=UTF-8 -classpath .::/m1/voyager
    voyager   3787     1  0 01:02 ?        00:00:36 java -Dlog4j.configuration=file:///m1/voyager/traindb/ini/ -Xms32m -Xmx64m -Dfile.encoding=UTF-8 -classpath .:/m1/voyager/li
    voyager   3842     1  0 01:02 ?        00:00:36 java -Dlog4j.configuration=file:///m1/voyager/traindb/ini/ -Xms32m -Xmx64m -Dfile.encoding=UTF-8 -classpath .::/m1/voyager/
    voyager  24750 24699  0 12:58 pts/0    00:00:00 grep -E --color=auto -i gdc|jobd
    [VGER] voyager@aio0009 : voyager/ $ 


    GDC can appear to be running but still be unresponsive. In that situation, as well as when it is not running, use the following instructions to restart GDC.

    Additional Information

    To restart GDC:

    Connect to the Voyager server and login as the voyager user

    Run "ps -efw | grep jobd||gdcsvr" to check for running gdcsvr and jobd processes. Make note of the PID of any running processes.

    Run "kill <PID>" for each running gdcsvr or jobd process. 

    cd m1/voyager/xxxdb/sbin



    The last two commands above restart jobd and gdcsvr by running "/m1/voyager/xxxdb/sbin/Pjobd" and "/m1/voyager/xxxdb/sbin/Pgdcsvr"

    After running those last two commands, recheck to see if GDC is once again running properly.

    See also: Jobs in GDC queue never start

    • Article last edited: 28-Jun-2019
    • Was this article helpful?