Advanced Global Data Services Troubleshooting
To troubleshoot GDS effectively, you must collect OPatch inventory, run scripted GDSCTL configuration and status commands, capture listener status, and gather logs/traces.
Use these steps to provide a good data pool for troubleshooting issues, and potentially to help Oracle Support assist you.
- Collecting patch information can be useful for code version-related issues:
$ cd $ORACLE_HOME/OPatch $ ./opatch lsinventory -detail > lsinventory_info.txt Collect all GDS configuration data. Save the following commands in a script and run it:
#!/bin/bash # Stop script if any command fails set -e # Check if gdsctl is available in PATH if ! command -v gdsctl &> /dev/null then echo "gdsctl could not be found. Please make sure it is installed and available in PATH." exit 1 fi echo "Starting gdsctl session..." # Start the gdsctl session gdsctl << EOF # List GSMs, GSM status echo "GDSCTL COMAND: config" config echo "GDSCTL COMAND: config gsm -gsm " #config gsm -gsm echo "GDSCTL COMAND: gsm status" gsm status # List services echo "GDSCTL COMAND: services" services echo "GDSCTL COMAND: config service -service " #config service -service # List databases echo "GDSCTL COMAND: databases" databases # Network echo "GDSCTL COMAND: config vncr" config vncr # Validate config echo "GDSCTL COMAND: validate" validate # End of gdsctl commands EOF echo "gdsctl session completed successfully." # Exit the script exit 0- Collect GSM listener status.
$ lsnrctl status
If it is necessary to contact Oracle Support, then the data you have collected with these procedures will prove useful.
In addition, the following files would also be helpful:
From GSM Host: $ORACLE_HOME/network/admin
From GSM Host: GSM alert log file
From GSM Host: GDSCTL.log
From GSM Host: GSM trace files located in
From GSM Host: lsinventory, lsinventory_info.txt
From GDS Catalog Host: lsinventory, lsinventory_info.txt
Parent topic: GDS Logs and Tracing