ASM was not starting up on remote node with CRS-0223/ORA-39511
(Doc ID 2762703.1)
Last updated on NOVEMBER 16, 2022
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterInformation in this document applies to any platform.
Symptoms
After node came up crs is not coming up.
On master node , we saw ,
2021-01-20 01:08:05.504 : CRSPE:3430356736: {1:38821:5133} evalStart() for
resource 'ora.asm' Checking permission for user 'grid'
2021-01-20 01:08:05.505 : CRSPE:3430356736: {1:38821:5133} RI is to process
state change [ora.asm 1 1] on [] : 1 <<---
2021-01-20 01:08:05.505 : CRSPE:3430356736: {1:38821:5133} m_allowedServer
cleared for ora.asm 1 1
resource 'ora.asm' Checking permission for user 'grid'
2021-01-20 01:08:05.505 : CRSPE:3430356736: {1:38821:5133} RI is to process
state change [ora.asm 1 1] on [] : 1 <<---
2021-01-20 01:08:05.505 : CRSPE:3430356736: {1:38821:5133} m_allowedServer
cleared for ora.asm 1 1
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 |