My Oracle Support Banner

FLEXASM: Unable to Start CRS After Reboot ORA-12537 ora.storage ORA-12547 (Doc ID 2294385.1)

Last updated on DECEMBER 31, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

This Document is applicable only for FLEX ASM configuration.

Good node ( Node 1)

CRS is up and running fine


SQL> select username from v$pwfile_users;

USERNAME
--------------------------------------------------------------------------------
SYS
CRSUSER__ASM_001
ASMSNMP

Bad node ( Node 2)

While starting CRS on node 2, CRSD and EVMD failed to start.

grid@node2 grid_12.2.0.1 +ASM2 $ crsctl check crs
CRS-4638: Oracle High Availability Services is online
CRS-4535: Cannot communicate with Cluster Ready Services <<< CRSD fails to start >>>
CRS-4529: Cluster Synchronization Services is online
CRS-4534: Cannot communicate with Event Manager  <<< EVMD fails to start >>>

ora.storage fails to start with the below error.

ohasd_orarootagent_root.trc
- - - - - - - - - -
2019-08-13 19:48:27.006 : USRTHRD:893126400: {0:5:3} 8154 Error 4 querying length of attr ASM_DISCOVERY_ADDRESS

2019-08-13 19:48:27.015 : USRTHRD:893126400: {0:5:3} 8154 Error 4 querying length of attr ASM_STATIC_DISCOVERY_ADDRESS

2019-08-13 19:48:27.084 : CLSCRED:893126400: (:CLSCRED1079:)clsCredOcrKeyExists: Obj dom : SYSTEM.credentials.domains.root.ASM.Self.303a14fb7cd04f7affd9f5ed7ebdcd83.root not found
2019-08-13 19:48:27.084 : USRTHRD:893126400: {0:5:3} 7872 Error 4 opening dom root in 0x7fd00820c3d0

2019-08-13 19:48:30.691 : USRTHRD:893126400: {0:5:3} ORA-12547: TNS:lost contact
ORA-12547: TNS:lost contact
ORA-15077: could not locate ASM instance serving a required diskgroup

 

Changes

Newly Implemented VNC (Valid Node checking) with all the required hosts in sqlnet.ora.

hostname restrictions in the sqlnet.ora

TCP.VALIDNODE_CHECKING = YES
TCP.INVITED_NODES=(all the required hosts for Valid node checking)

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.