Wednesday, 2 September 2015

Important Logs for investigating Cluster Logs

Information from ALL nodes in order to investigate any Cluster HAIP Issue :

0. ping all the scan IPs, tnsping the listener and check if the listener is being resolved by scan name.
1. upload endpoints_listener.ora, listener.ora, tnsnames.ora and sqlnet.ora You are using
2. provide output of (from all nodes):
$GRID_HOME/bin/crsctl stat res -t
$GRID_HOME/bin/crsctl stat res -t -init
srvctl config
$GRID_HOME/bin/srvctl config scan
$GRID_HOME/bin/srvctl config scan_listener
$GRID_HOME/bin/srvctl config listener
$GRID_HOME/bin/lsnrctl status LISTENER_SCAN1
$GRID_HOME/bin/lsnrctl status LISTENER_SCAN2
$GRID_HOME/bin/lsnrctl status LISTENER_SCAN3
$GRID_HOME/bin/lsnrctl service LISTENER_SCAN1
$GRID_HOME/bin/lsnrctl service LISTENER_SCAN2
$GRID_HOME/bin/lsnrctl service LISTENER_SCAN3
$GRID_HOME/bin/lsnrctl status LISTENER
$GRID_HOME/bin/lsnrctl service LISTENER
from sql connection to each instance:
show parameter remote_listener
show parameter local_listener

3. Upload local and scan_listener logs from all nodes.
a) listener.log

b) Please find the location for SCAN listeners and upload the files

=>  $GRID_HOME/log/diag/tnslsnr//listener_scan1/trace/listener_scan1.log

    $GRID_HOME/log/diag/tnslsnr//listener_scan2/trace/listener_scan2.log

    $GRID_HOME/log/diag/tnslsnr//listener_scan3/trace/listener_scan3.log

4. cat /etc/hosts
5. CRS Logs:
    1. Clusterware alert log in /log/
    2. The cssdagent log(s) in /log//agent/ohasd/oracssdagent_root
    3. The cssdmonitor log(s) in /log//agent/ohasd/oracssdmonitor_root
    4. The ocssd log(s) in /log//cssd
    5. The lastgasp log(s) in /etc/oracle/lastgasp or /var/opt/oracle/lastgasp
    6. IPD/OS or OS Watcher data
    7. 'opatch lsinventory -detail' output for the GRID home
    8. *Messages files:

* Messages file locations:

    Linux: /var/log/messages
    Sun: /var/adm/messages
    HP-UX: /var/adm/syslog/syslog.log
    IBM: /bin/errpt -a > messages.out