ODA Trace files Show ORA 15041 ; Error 19504 Creating Archive log ; ORA 312 after crash - Some Activity Caused Archivelog Full and Now Multiple Databases Will Not Come Up :
(Doc ID 1673290.1)
Last updated on SEPTEMBER 01, 2023
Applies to:
Oracle Database Appliance Software - Version 2.1.0.1 to 12.1.2.12.0 [Release 2.1 to 12.1]Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X4-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
This problem is the result of filling up the diskgroup storage: (RECO).
Sometimes the problem source is more evident than others as error messages may or may not point directly to the problem source.
In this case during an Import it appears that the archivelog destination was full and now all databases will hang.
Running out of storage or space for databases or any functionality can result in hanging symptoms
- For this reason space should always be considered as a possible source for problems with incomplete operations from the OS up to applications or the database(s).
In this case during an Import it appears that the archivelog destination was full and now all databases will hang.
Running out of storage or space for databases or any functionality can result in hanging symptoms
- For this reason space should always be considered as a possible source for problems with incomplete operations from the OS up to applications or the database(s).
As the symptom includes the database(s) crashing we can look in the ALERT.LOGs for evidence
DATABASE ALERT.LOG
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! |