RAC on Windows: Grid Infrastructure Resource 'ora.asm' State Details of 'Under THA, Starting' and Clusterware Stack Takes a Long Time to Start
(Doc ID 2246721.1)
Last updated on FEBRUARY 24, 2022
Applies to:Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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 Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Microsoft Windows x64 (64-bit)
Starting Oracle Grid Infrastructure stack seems to 'suddenly' have started taking a very long time. While observing the startup (using the command 'crsctl stat res -t -init') we are able to 'catch' the ora.asm resource with a TARGET of ONLINE, but remaining in a STATE of OFFLINE for a long time and showing STATE DETAILS: 'Under THA, Starting'
This issue may be observed whenever the Grid Infrastructure stack is stopped / started, such as:
1. explicitly issuing 'crsctl stop crs' or 'crsctl start crs'
2. rebooting the cluster nodes (forcing a restart of Oracle Clusterware)
3. while patching, such as when running 'rootcrs.pl -prepatch' and/or 'rootcrs.pl -postpatch' since those scripts include stopping and starting of CRS
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