Veritas Storage Foundation 5.1 SP1 for Oracle RAC Administrator"s Guide (5900-1512, April 2011)

This GAB logging daemon collects the GAB related logs when a critical events
such as an iofence or failure of the master of any GAB port occur, and stores the
data in a compact binary form. You can use the gabread_ffdc utility as follows
to read the GAB binary log files:
/opt/VRTSgab/gabread_ffdc binary_logs_files_location
You can change the values of the following environment variables that control
the GAB binary log files:
■ GAB_FFDC_MAX_INDX: Defines the maximum number of GAB binary log files
The GAB logging daemon collects the defined number of log files each of eight
MB size. The default value is 20, and the files are named gablog.1 through
gablog.20. At any point in time, the most recent file is the gablog.1 file.
■ GAB_FFDC_LOGDIR: Defines the log directory location for GAB binary log
files
The default location is:
/var/adm/gab_ffdc
Note that the gablog daemon writes its log to the glgd_A.log and glgd_B.log
files in the same directory.
You can either define these variables in the following GAB startup file or use the
export command. You must restart GAB for the changes to take effect.
/etc/rc.config.d/gabconf
Gathering LLT and GAB information for support analysis
You must run the getcomms script to gather LLT and GAB information when you
encounter issues with LLT and GAB.
To gather LLT and GAB information for support analysis
1
If you had changed the default value of the GAB_FFDC_LOGDIR parameter,
you must again export the same variable before you run the getcomms script.
See “GAB message logging” on page 169.
2
Run the following command on each node to gather information:
# /opt/VRTSgab/getcomms -local
Troubleshoot and fix the issue.
If the issue cannot be fixed, then contact Symantec technical support with
the file /tmp/commslog.time_stamp.tar that the getcomms script generates.
Troubleshooting SF Oracle RAC
About troubleshooting SF Oracle RAC
170