Database Reference
In-Depth Information
Operating system (OS) logs
: Referring to the OS-specific log file will be hugely helpful in identifying
Clusterware startup and shutdown issues. Different platforms maintain logs at different locations, as shown in the
following example:
HPUX - /var/adm/syslog/syslog.log
AIX - /bin/errpt -a
Linux - /var/log/messages
Windows - Refer .TXT log files under Application/System log using Windows Event Viewer
Solaris - /var/adm/messages
■
oracle Clusterware generates and maintains 0-sized socket files in the hidden
'./oracle'
directory
under the location
/etc
or
/var/tmp
(according to the platform). removing these files as part of regular log cleanup or
unintentionally removing them might lead to a cluster hung situation.
Caution
■
it is mandatory to maintain sufficient free space under the file system on which grid and rdbsM software are
installed to prevent Clusterware issues; in addition, oracle suggests not to remove the logs manually.
Note
Oracle Clusterware Troubleshooting - Tools and Utilities
Managing and troubleshooting various issues related to Clusterware and its components are two of the key
responsibilities of any Oracle DBA. Oracle provides a variety of tools and utilities in this context that the DBA can
use to monitor Clusterware health and also diagnose and troubleshoot any serious Clusterware issues. Some of the
key tools and utilities that Oracle provides are as follows:
CHM, diagcollection.sh
,
ProcWatcher
,
RACcheck
,
oratop
,
OSWatcher Black Box Analyzer (OSWbba)
,
The Light on-board monitor (LTOM)
,
Hang File Generator (HANGFG)
.
In the following sections, we will cover some of the uses of these very important tools and describe their
advantages.
Cluster Health Check with CVU
Starting with 11.2.0.3, the cluster verification utility (
cluvfy
) is capable of carrying out the post-Clusterware and
Database installation health checks. With the new
-healthcheck
argument, cluster and database components best
practices, mandatory requirements, deviation, and proper functionality can be verified.
The following example collects detailed information about best-practice recommendations for Clusterware in an
HTML file named
cvucheckreport_<timestamp>.htm
:
$./cluvfy comp healthcheck -collect cluster -bestpractice -html
When no further arguments are attached with the
healthcheck
parameter, the Clusterware and Database checks
are carried out. Use the following example to perform the health checks on the cluster and database because no
-html
argument was specified; the output will be stored in a text file:
$./cluvfy comp healthcheck
