12c:GIMR fails to start during post patch steps
(Doc ID 2162581.1)
Last updated on DECEMBER 20, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.2.0.1 [Release 12.1 to 12.2]Oracle 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 Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
GIMR fails to start returning messages similar to the following.
Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [ROLLING PATCH]. The cluster active patch level is [2278979115].
PRCR-1005 : Resource ora.mgmtdb is already stopped
PRCR-1013 : Failed to start resource ora.mgmtdb
PRCR-1064 : Failed to start resource ora.mgmtdb on node reocmp310or
CRS-2549: Resource 'ora.mgmtdb' cannot be placed on '<node1>' as it is not a valid candidate as per the placement policy
2016/04/26 13:49:51 CLSRSC-490: Starting the Grid Infrastructure Management Repository database failed.
PRCR-1005 : Resource ora.mgmtdb is already stopped
PRCR-1013 : Failed to start resource ora.mgmtdb
PRCR-1064 : Failed to start resource ora.mgmtdb on node reocmp310or
CRS-2549: Resource 'ora.mgmtdb' cannot be placed on '<node1>' as it is not a valid candidate as per the placement policy
2016/04/26 13:49:51 CLSRSC-490: Starting the Grid Infrastructure Management Repository database failed.
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 |