Storage Foundation for Oracle® RAC 7.3.1 Administrator's Guide - Linux
- Section I. SF Oracle RAC concepts and administration
- Overview of Storage Foundation for Oracle RAC
- About Storage Foundation for Oracle RAC
- Component products and processes of SF Oracle RAC
- About Virtual Business Services
- Administering SF Oracle RAC and its components
- Administering SF Oracle RAC
- Starting or stopping SF Oracle RAC on each node
- Administering VCS
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- Administering the CP server
- Administering CFS
- Administering CVM
- Changing the CVM master manually
- Administering Flexible Storage Sharing
- Backing up and restoring disk group configuration data
- Administering SF Oracle RAC global clusters
- Administering SF Oracle RAC
- Overview of Storage Foundation for Oracle RAC
- Section II. Performance and troubleshooting
- Troubleshooting SF Oracle RAC
- About troubleshooting SF Oracle RAC
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the SF Oracle RAC cluster nodes
- Issues during online migration of coordination points
- Troubleshooting Cluster Volume Manager in SF Oracle RAC clusters
- Troubleshooting CFS
- Troubleshooting interconnects
- Troubleshooting Oracle
- Troubleshooting ODM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
GAB message logging
If GAB encounters some problem, then First Failure Data Capture (FFDC) logs are also generated and dumped.
When you have configured GAB, GAB also starts a GAB logging daemon (/opt/VRTSgab/gablogd
). GAB logging daemon is enabled by default. You can change the value of the GAB tunable parameter gab_ibuf_count to disable the GAB logging daemon.
See About GAB load-time or static tunable parameters.
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-kernel_version 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
throughgablog.20
. At any point in time, the most recent file is thegablog.1
file.GAB_FFDC_LOGDIR: Defines the log directory location for GAB binary log files
The default location is:
/var/log/gab_ffdc
Note that the gablog daemon writes its log to the
glgd_A.log
andglgd_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/sysconfig/gab