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

Original string: clust_run=`$VXCLUSTADM -m vcs -t $TRANSPORT

startnode 2> $CVM_ERR_FILE`

Modified string: clust_run=`$VXCLUSTADM -m vcs -t $TRANSPORT -T

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/adm/messagesfile

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 -k 2000 > \

/var/adm/vx/kmsgdump.out

GAB message logging

If GAB encounters some problem, then First Failure Data Capture (FFDC) logs are

also generated and dumped along with other core dumps and stack traces.

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” on page 244.

169Troubleshooting SF Oracle RAC

About troubleshooting SF Oracle RAC