Database Reference
In-Depth Information
When the CRSD fails to start up, or is unhealthy, refer to this file to find out the root cause of the problem.
ohasd.log
: The Oracle High Availability Service daemon (
OHASD
), a new cluster stack, was first introduced with
11gR2 to manage and control the other cluster stack. The primary responsibilities include managing OLR;
starting, stopping, and verifying
cluster health status on the local and remote nodes; and also supporting
cluster-wide commands. The process maintains a log file named
crsd.log
under the
$GIRD_HOME/log/<hostname>/
ohasd
location and writes all important event messages in the log file. Examine the file when you face issues running
root.sh script, such as when the
ohasd
process fails to start up or in case of OLR corruption.
Oracle certainly doesn't encourage deleting the log file for any reason, as it is governed by Oracle automatically.
The file will be archived as
ohasd.l01
under the same location on reaching a size of 10 MB, and a fresh log file
(
ohasd.log
) will be generated. Like
crsd.log
and
crs.log
, there will be ten archived copies kept for future reference
in the same directory.
2013-04-17 11:32:47.096: [ default][1] OHASD Daemon Starting. Command string :reboot
2013-04-17 11:32:47.125: [ default][1] Initializing OLR
2013-04-17 11:32:47.255: [ OCRRAW][1]proprioo: for disk 0
(/u00/app/12.1.0/grid_1/cdata/rac2.olr), id match (1), total id sets,
need recover (0), my votes (0), total votes (0), commit_lsn (3118), lsn (3118)
2013-04-17 11:32:47.368: [ default][1] Loading debug levels . . .
2013-04-17 11:32:47.803: [ clsdmt][13]Creating PID [6401] file for home
/u00/app/12.1.0/grid_1 host usdbp10 bin ohasd to /u00/app/12.1.0/grid_1/ohasd/init/
Upon successful execution of
ocrdump, ocrconfig, olsnodes, oifcfg,
and
ocrcheck
commands, a log file will
be generated under the
$GRID_HOME/log/<hostname>/client
location. For EVM daemon (EVMD) process-relevant
details, look at the
evmd.log
file under the
$GRID_HOME/log<hostname>/evmd
location. Cluster Health Monitor
Services (
CHM
) and logger services are maintained under the
$GRID_HOME/log/<hostname>/crfmond, crflogd
directories.
Figure
2-4
depicts the hierarchy of the Clusterware component directory structure.
Figure 2-4.
Unified Clusterware log directory hierarchy
