DB Instance is terminated due to ORA-15064 after Server down
(Doc ID 2196269.1)
Last updated on FEBRUARY 12, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 12.1.0.2 [Release 10.1 to 12.1]Oracle Database - Standard Edition - Version 10.1.0.2 to 12.1.0.2 [Release 10.1 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Symptoms
DB Instance of surviving node may be terminated due to ORA-15064 on RAC env after one Server Down.
Mon Apr 18 16:15:39 2016
Beginning instance recovery of 1 threads
Abort recovery for domain 0
ORA-38701 occurred during recovery, instance will be terminated
Mon Apr 18 16:15:39 2016
ORA-38701: Flashback database log 19 seq 236 thread 1: <file path of flashback log>
ORA-17503: ksfdopn:2 Failed to open file <file path of flashback log>
ORA-15064: Initialization parameters prevent client from being enabled.
SMON (ospid: 3355): terminating the instance due to error 38701
Beginning instance recovery of 1 threads
Abort recovery for domain 0
ORA-38701 occurred during recovery, instance will be terminated
Mon Apr 18 16:15:39 2016
ORA-38701: Flashback database log 19 seq 236 thread 1: <file path of flashback log>
ORA-17503: ksfdopn:2 Failed to open file <file path of flashback log>
ORA-15064: Initialization parameters prevent client from being enabled.
SMON (ospid: 3355): terminating the instance due to error 38701
This problem may happen under following situations.
- Database is configured as RAC
- Files of Database are located on ASM
- DB instance and ASM instance on same node are terminated simultaneously.
Changes
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 |
| References |