Start/Stop of ora.ons fails with CRS-2680, CRS-5804
(Doc ID 1641778.1)
Last updated on MARCH 24, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
ONS has an inconsistent state and cannot be stopped or started successfully:
# crsctl stat res ora.ons -t
--------------------------------------------------------------------------------
NAME TARGET STATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ons
ONLINE UNKNOWN <nodename1>
OFFLINE UNKNOWN <nodename2>
--------------------------------------------------------------------------------
NAME TARGET STATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ons
ONLINE UNKNOWN <nodename1>
OFFLINE UNKNOWN <nodename2>
Stopping ora.ons using the force option fails with below errors:
# crsctl stop res ora.ons -f
CRS-2679: Attempting to clean 'ora.ons' on '<nodename2>'
CRS-2679: Attempting to clean 'ora.ons' on '<nodename1>'
CRS-2680: Clean of 'ora.ons' on '<nodename2>' failed
CRS-5804: Communication error with agent process
CRS-2680: Clean of 'ora.ons' on '<nodename1>' failed
CRS-5804: Communication error with agent process
CRS-4000: Command Stop failed, or completed with errors.
CRS-2679: Attempting to clean 'ora.ons' on '<nodename2>'
CRS-2679: Attempting to clean 'ora.ons' on '<nodename1>'
CRS-2680: Clean of 'ora.ons' on '<nodename2>' failed
CRS-5804: Communication error with agent process
CRS-2680: Clean of 'ora.ons' on '<nodename1>' failed
CRS-5804: Communication error with agent process
CRS-4000: Command Stop failed, or completed with errors.
oraagent_oracle.log reports *ASSERTION FAILURE* during the stop:
Changes
Could occur after patch application or upgrade.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |