Database crashed with Control file sequence number mismatch during RMAN backup
(Doc ID 2823760.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterInformation in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data
from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material.
Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
Target Database crashed with the below errors when RMAN archive log backup was running:
2021-11-10T13:07:49.725628+01:00
NET (PID:18549): Archived Log entry 8007 added for T-1.S-5105 ID 0xbe7ad98f LAD:1
2021-11-10T13:08:11.322002+01:00
USER (ospid: 18555): terminating the instance
2021-11-10T13:08:11.373196+01:00
System state dump requested by (instance=1, osid=18555), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/target_database/target_database/trace/target_database_diag_55818.trc
2021-11-10T13:08:11.870375+01:00
ORA-1092 : opitsk aborting process
2021-11-10T13:08:15.116190+01:00
Dumping diagnostic data in directory=[cdmp_20211110130811], requested by (instance=1, osid=18555), summary=[abnormal instance termination].
2021-11-10T13:08:16.397942+01:00
Instance terminated by USER, pid = 18555
2021-11-15T10:00:31.140365+01:00
Starting ORACLE instance (normal) (OS id: 3907)
2021-11-15T10:00:31.163226+01:00
A normal startup started the database without issues.
Changes
None.
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 |