The RAC Node Eviction Troubleshooting tool will provide recommendations to resolve RAC Node Evictions by analyzing uploaded files. When a known solution is available, the tool will display the symptoms and causes which can lead to the issue and one or more suggestions for resolving the issue.
Benefits of using the RAC Node Eviction Troubleshooting tool:
• Analyzes uploaded files to provide recommendations when a known solution is available
• Troubleshooting report can be saved for later use
• Diagnostic Guide is available
• Create SR option available which will automatically populate many of the SR fields In order to troubleshoot a RAC Node Eviction issue using this tool, it will be necessary to provide the following information:
Evicted node name 2 methods for determine the name of the evicted node are:
• Login to the node which was evicted and type:
#uname -n
• Check the messages in the clusterware alert.log for a list of node names in the cluster. Look for " Reconfiguration Complete" in the log file. The list of nodes will be included in the message. Example CRS-1601: CSSD Reconfiguration complete. Active nodes are node21 node22 . Exact date and time of eviction
• In case of actual reboot of a node, you can use the following command to get exact date and time of reboot
#last reboot
reboot system boot 2.6.18-274.0.0.0 Wed Dec 27 15:26 (10+00:58)
reboot system boot 2.6.18-274.0.0.0 Thu Dec 28 13:10 (18+03:15)
•In case of reboot less eviction, please check clusterware alert.log for exact date and time when clusterware was restarted.
Example in alert log file,
2023-12-28 09:49:45.219 [cssd(2254)]CRS-1601:CSSD Reconfiguration complete. Active nodes are rac3 rac4.
The above log indicates that clusterware restarted at 2023-12-28 09:49:45.219
Linux/UNIX 11gR2/12.1.0.1/19c
Execute the following as root user:
# script /tmp/diag.log
# id
# env
# cd <temp-directory-with-plenty-free-space>
# $GRID_HOME/bin/diagcollection.sh
# exit
The following .gz files will be generated in the current directory and need to be uploaded along with /tmp/diag.log:
crsData_<hostname>.tar.gz,
ocrData_<hostname>.tar.gz,
oraData_<hostname>.tar.gz,
coreData_<hostname>.tar.gz (only --core option specified)
os_<hostname>.tar.gz
Please ensure all above information are provided from all the nodes.
