Clusterware fail to start CRS-5809 and CRS-2680 after the roll back of a 12c OCW PSU
(Doc ID 2051046.1)
Last updated on APRIL 12, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The clusterware startup when running the post patch script ("rootcrs.pl -postpatch" or "rootcrs.pl -patch) may fail with the below errors.
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on '<HOSTNAME>'
CRS-2679: Attempting to clean 'ora.gipcd' on '<HOSTNAME>'
CRS-5809: Failed to execute 'ACTION_SCRIPT' value of '' for 'ora.gipcd'. Error information 'cmd not found', Category : -2, OS error : 2
CRS-5809: Failed to execute 'ACTION_SCRIPT' value of '' for 'ora.gipcd'. Error information 'cmd not found', Category : -2, OS error : 2
CRS-2680: Clean of 'ora.gipcd' on '<HOSTNAME>' failed
CRS-2799: Failed to shut down resource 'ora.gipcd' on '<HOSTNAME>'
CRS-2795: Shutdown of Oracle High Availability Services-managed resources on '<HOSTNAME>' has failed
CRS-4687: Shutdown command has completed with errors.
CRS-4000: Command Stop failed, or completed with errors
CRS-2679: Attempting to clean 'ora.gipcd' on '<HOSTNAME>'
CRS-5809: Failed to execute 'ACTION_SCRIPT' value of '' for 'ora.gipcd'. Error information 'cmd not found', Category : -2, OS error : 2
CRS-5809: Failed to execute 'ACTION_SCRIPT' value of '' for 'ora.gipcd'. Error information 'cmd not found', Category : -2, OS error : 2
CRS-2680: Clean of 'ora.gipcd' on '<HOSTNAME>' failed
CRS-2799: Failed to shut down resource 'ora.gipcd' on '<HOSTNAME>'
CRS-2795: Shutdown of Oracle High Availability Services-managed resources on '<HOSTNAME>' has failed
CRS-4687: Shutdown command has completed with errors.
CRS-4000: Command Stop failed, or completed with errors
This is usually seen during the roll back to 12.1.0.2.2OCWPSU or lower, after applying a higher PSU. For Engineered Systems customers, rollback to 12.1.0.2.4DBBP or lower could cause this issue.
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 |
| Cause |
| Solution |
| References |