Database Reference
In-Depth Information
The following output will be displayed on your screen:
CRS-2679: Attempting to clean 'ora.cssdmonitor' on 'rac1'
CRS-2681: Clean of 'ora.cssdmonitor' on 'rac1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'rac1'
CRS-2676: Start of 'ora.cssdmonitor' on 'rac1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'rac1'
CRS-2676: Start of 'ora.cssd' on 'rac1' succeeded
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'rac1'
CRS-2672: Attempting to start 'ora.crsd' on 'rac1'
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'rac1' succeeded
CRS-2676: Start of 'ora.crsd' on 'rac1' succeeded
CRSD startup issues -
When the CRSD-related startup and other issues are being reported, the following
guidelines provide assistance to troubleshoot the root cause of the problem:
CRS-4535: Cannot communicate with CRS:
Verify the CRSD process on the OS:
ps -ef |grep crsd.bin
Examine the
crsd.log
to look for any possible causes that prevent the CRSD from starting.
Ensure that the node can access the OCR files; run the
'ocrcheck'
command to verify. If the node can't access
the OCR files, check the following:
Check the OCR disk permission and ownership.
If OCR is placed on the ASM diskgroup, ensure that the ASM instance is up and that the appropriate diskgroup is
mounted.
Repair any OCR-related issue encountered, if needed.
Use the following command to ensure that the CRSD daemon process is ONLINE:
$ crsctl stat res -init -t
--------------------------------------------------------------------------------
NAME TARGET STATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.crsd
1 ONLINE OFFLINE rac1
You can also start the individual daemon manually using the following command:
$GRID_HOME/bin/crsctl start res ora.cssd -init
In case the Grid Infrastructure malfunctions or its resources are reported as being unhealthy, you need to ensure
the following:
$GRID_HOME
and
$ORACLE_HOME
filesystem for
the cluster to write the events in the respective logs for each component.
•
Sufficient free space must be available under the
•
Ensure enough system resource availability, in terms of CPU and memory.
•
Start up any individual resource that is OFFLINE.
