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
Question
How can I tell if Global Data Change (GDC) is running?
Answer
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.
GDC may be running for one database instance (e.g., traindb) but not for the production instance. In that situation you will see something like this:
[VGER] voyager@aio0002 : voyager/ $ ps -efw |egrep -i "gdc|jobd"
voyager 2812 1 0 01:03 ? 00:00:51 java -Dlog4j.configuration=file:///m1/voyager/traindb/ini/gdc-log4j.properties -Xms32m -Xmx64m -XX:+UseConcMarkSweepGC -Dfile.encoding=UTF-8 -classpath .:/m1
voyager 2830 1 0 01:03 ? 00:00:55 java -Dlog4j.configuration=file:///m1/voyager/traindb/ini/jobd-log4j.properties -Xms32m -Xmx64m -XX:+UseConcMarkSweepGC -Dfile.encoding=UTF-8 -classpath .::/
voyager 24376 24333 0 14:10 pts/0 00:00:00 grep -E --color=auto -i gdc|jobd
This following is an example of what you might see if GDC is running for both the traindb instance and the xxxdb (aka: production) instance:
[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/gdc-log4j.properties -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/jobd-log4j.properties -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/gdc-log4j.properties -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/jobd-log4j.properties -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 |egrep -i "gdc|jobd" to check for running gdcsvr and jobd processes for the appropriate instance. Make note of the PID of any running processes.
Run "kill <PID>" for each running gdcsvr or jobd process if necessary.
cd m1/voyager/xxxdb/sbin
./Pgdcsvr
./Pjobd
The last two commands that are shown 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
- Voyager Global Data Change job does not change status from Kill to Killed
- Article last edited: 28-Jun-2019