Troubleshooting Clusterware startup problems with DTRACE

Debug CW startup problems with DTRACE  – Different Case studies

During the testing we will rate 3 different tools : DTRACE, Cluvfy and READ Tracefiles
All Debug utils get rated with up to 5 stars : ***** stars depending on usage
Case I   : Any execve() errors for all executables like:  crsd.bin
DTRACE        : ***
CLUVFY        : *****  [ most useful tool ]
Reading Traces: *
Comment       : Debugging steps are the same for all CW executables
Case II  : Open errors for files HOSTNAME.pid like hract21.pid
DTRACE        : ***** [ most useful tool ]
CLUVFY        :
Reading Traces: *
Comment       : Debugging steps are the same for all CRS components
Case III : Open errors for special socket files like : /var/tmp/.oracle/ora_gipc_GPNPD_hract21_lock
Open errors for files HOSTNAME.pid like hract21.pid
DTRACE        : *****  [ most useful tool ]
CLUVFY        :
Reading Traces: **
Comment       : Debugging steps are the same for all CRS components
Case IV  : GPNPD  doesn't start - mismatch between profile.xml and the PRIVATE INTERFACE address
DTRACE        :
CLUVFY        : *****  [ most useful tool ]
Reading Traces: **
Case V   : GIPCD  doesn't start - mismatch between profile.xml and the PUBLIC  INTERFACE address
DTRACE        : ****
CLUVFY        : *****  [ most useful tool ]
Reading Traces: **
Case VI  : CSSD doesn't start as Port 42424 is already in use
DTRACE        : *****  [ most useful tool ]
CLUVFY        :
Reading Traces: *
Case VII : CSSD,GIPCD doesn't start as Port 5353 is already in use
DTRACE        : *****  [ most useful tool ]
CLUVFY        :
Reading Traces: *
Case VIII: GIPCD, GPNPD CSDD not starting as Nameserver is not reachable
          [ ECONNREFUSED    111 -> Connection refused ]
DTRACE        : ***
CLUVFY        : *****  [ most useful tool ]
Reading Traces: *
    • Note : CLUVFY is no always the best choice to debug CW startup problems.
    • DTRACE is an easy to use utility and any DBA should use this utiltiy in its production env as it can can reduce the error solving process a lot !!

2 thoughts on “Troubleshooting Clusterware startup problems with DTRACE”

Leave a Reply

Your email address will not be published. Required fields are marked *