Storage Foundation for Oracle® RAC 7.4.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
Collecting important CVM logs
You need to stop and restart the cluster to collect detailed CVM TIME_JOIN messages.
To collect detailed CVM TIME_JOIN messages
- On all the nodes in the cluster, perform the following steps.
Edit the /opt/VRTSvcs/bin/CVMCluster/online script.
Insert the '-T' option to the following string.
Original string: clust_run='LANG=C LC_MESSAGES=C $VXCLUSTADM -m vcs -t $TRANSPORT startnode 2> $CVM_ERR_FILE'
Modified string: clust_run='LANG=C LC_MESSAGES=C $VXCLUSTADM -T -d -m vcs -t $TRANSPORT startnode 2> $CVM_ERR_FILE'
- Stop the cluster.
# hastop -all
- Start the cluster.
# hastart
At this point, CVM TIME_JOIN messages display in the
/var/log/messages
file and on the console.
You can also enable vxconfigd daemon logging as follows:
# vxdctl debug 9 /var/adm/vx/vxconfigd_debug.out
The debug information that is enabled is accumulated in the system console log and in the text file /var/adm/vx/vxconfigd_debug.out
. '9' represents the level of debugging. '1' represents minimal debugging. '9' represents verbose output.
Caution:
Turning on vxconfigd debugging degrades VxVM performance. Use vxconfigd debugging with discretion in a production environment.
To disable vxconfigd debugging:
# vxdctl debug 0
The CVM kernel message dump can be collected on a live node as follows:
# /etc/vx/diag.d/kmsgdump -d 2000 > \ /var/adm/vx/kmsgdump.out