DB provisioning fails :ERROR: rac _dbhealthcheck : timed out: only 3 out of 4 instances are open READ WRITE
(Doc ID 2776773.1)
Last updated on DECEMBER 12, 2022
Applies to:
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]Information in this document applies to any platform.
Symptoms
DB provisioning fails.
ocde log shows:
....
2021-05-13 13:54:22.341179 - DEBUG: SQL Executing set hea off set pagesize 5000 set linesize 400 set newpage none set feedback off prompt =START= select count(1) from sys.gv$database where open_mode = 'READ WRITE'; quit
2021-05-13 13:54:22.412916 - INFO: rac _dbhealthcheck : DB not really up yet, DB reporting 3 out of 4 instances are open READ WRITE on try 120
2021-05-13 13:54:37.413516 - ERROR: rac _dbhealthcheck : timed out: only 3 out of 4 instances are open READ WRITE
2021-05-13 13:54:22.341179 - DEBUG: SQL Executing set hea off set pagesize 5000 set linesize 400 set newpage none set feedback off prompt =START= select count(1) from sys.gv$database where open_mode = 'READ WRITE'; quit
2021-05-13 13:54:22.412916 - INFO: rac _dbhealthcheck : DB not really up yet, DB reporting 3 out of 4 instances are open READ WRITE on try 120
2021-05-13 13:54:37.413516 - ERROR: rac _dbhealthcheck : timed out: only 3 out of 4 instances are open READ WRITE
Node 3 CRS alert log shows failure during startup of the instance
2021-05-13 13:24:27.587 [ORAAGENT(297912)]CRS-5017: The resource action "ora.<dbname>_us0etm1t01c1.db start" encountered the following error:
2021-05-13 13:24:27.587 ORA-12649: Unknown encryption or data integrity algorithm
2021-05-13 13:24:27.587 ORA-12649: Unknown encryption or data integrity algorithm
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 |