Problem phenomenon
After using shutdown abort to stop Dataguard Standby library, the library can not open, reported ORA-01196 error.
Specific as follows:
Found a standby library can not apply the log, view the repository log did not find an error, suspect that the standby Library application log service stopped, so try to restart the repository;
May be because the standby library is busy reading business, shutdown immediate shut down the standby time is too long, so the use of the Shutdown Abort command;
However, the following error occurred in the boot repository, resulting in data file corruption, control files and data file The SCN number is inconsistent.
--Start the Library times wrong
Sql> Startup
The ORACLE routine has been started.
Total System Global area 2.0310E+10 bytes
Fixed Size 2235256 bytes
Variable Size 9328133256 bytes
Database buffers 1.0939E+10 bytes
Redo buffers 40894464 bytes
The database is loaded.
Ora-10458:standby Database Requiresrecovery
ORA-01196: File 1 inconsistent due to media recovery session failure
ORA-01110: Data file 1: ' +data/htdb5/datafile/system.261.759082693 '
--View Log
ALTER DATABASE Open
Data Guard brokerinitializing ...
Data Guard brokerinitialization Complete
Beginning standby crash recovery.
Serial Media Recovery started
Managed Standby recoverystarting Real time Apply
Media Recovery log+fra/htdb5/archivelog/2015_07_16/thread_1_seq_180068.1541.885192077
Thu Jul 16 12:00:47 2015
Errors in FILE/U01/APP/ORA11G/DIAG/RDBMS/HTDB5/HTDB5/TRACE/HTDB5_ORA_10154.TRC:
ORA-01013: User requests cancellation of current operation
Ora-10567:redo is Inconsistentwith data block (file#, block# 1187724, file offset is 1139900416 bytes)
Ora-10564:tablespace Jdywp_idx
ORA-01110: Data file: ' +data/htdb5/datafile/jdywp_idx.336.856967805 '
Ora-10561:block type ' TRANSACTION MANAGED INDEX block ', Data object# 251837
Errors in FILE/U01/APP/ORA11G/DIAG/RDBMS/HTDB5/HTDB5/TRACE/HTDB5_ORA_10154.TRC:
ORA-00339: Archive logs do not contain any redo
ORA-00334: Archive log: ' +data/htdb5/onlinelog/group_2.280.759082845 '
Ora-10567:redo is Inconsistentwith data block (file#, block# 1187724, file offset is 1139900416 bytes)
Ora-10564:tablespace Jdywp_idx
ORA-01110: Data file: ' +data/htdb5/datafile/jdywp_idx.336.856967805 '
Ora-10561:block type ' TRANSACTION MANAGED INDEX block ', Data object# 251837
Errors in File/u01/app/ora11g/diag/rdbms/htdb5/htdb5/trace/htdb5_ora_10154.trc (incident=116743):
ORA-00600: Internal error code, parameters: [3020],[47], [1187724], [198320012], [], [], [], [], [], [], [], []
Ora-10567:redo is Inconsistentwith data block (file#, block# 1187724, file offset is 1139900416 bytes)
Ora-10564:tablespace Jdywp_idx
ORA-01110: Data file: ' +data/htdb5/datafile/jdywp_idx.336.856967805 '
Ora-10561:block type ' TRANSACTION MANAGED INDEX block ', Data object# 251837
Incident Details IN:/U01/APP/ORA11G/DIAG/RDBMS/HTDB5/HTDB5/INCIDENT/INCDIR_116743/HTDB5_ORA_10154_I116743.TRC
Use Adrci or support Workbenchto package the incident.
See Note 411.1 at My oraclesupport for error and packaging details.
Standby Crash recovery Aborteddue to error 600.
Errors in FILE/U01/APP/ORA11G/DIAG/RDBMS/HTDB5/HTDB5/TRACE/HTDB5_ORA_10154.TRC:
ORA-00600: Internal error code, parameters: [3020],[47], [1187724], [198320012], [], [], [], [], [], [], [], []
Ora-10567:redo is Inconsistentwith data block (file#, block# 1187724, file offset is 1139900416 bytes)
Ora-10564:tablespace Jdywp_idx
ORA-01110: Data file: ' +data/htdb5/datafile/jdywp_idx.336.856967805 '
Ora-10561:block type ' TRANSACTION MANAGED INDEX block ', Data object# 251837
Recovery interrupted!
Some recovered datafiles maybeleft Media fuzzy
Media recovery may continue butopen resetlogs may fail
Completed standby crashrecovery.
Errors in FILE/U01/APP/ORA11G/DIAG/RDBMS/HTDB5/HTDB5/TRACE/HTDB5_ORA_10154.TRC:
Ora-10458:standby databaserequires Recovery
ORA-01196: File 1 inconsistent due to media recovery session failure
ORA-01110: Data file 1: ' +data/htdb5/datafile/system.261.759082693 '
ORA-10458 signalled during:alter database open ...
Thu Jul 16 12:00:49 2015
Sweep [inc][116743]: Completed
Sweep [inc2][116743]: Completed
Thu Jul 16 12:00:49 2015
Dumping diagnostic data indirectory=[cdmp_20150716120049], requested by (Instance=1, osid=10154), summary=[incident= 116743].
Thu Jul 16 12:01:50 2015
Workaround:
The point at which the standby is flashed back to its normal state.
--If the database flashback was opened before
Sql> select flashback_on from V$database;
flashback_on
------------------
YES
sql> Flashback Database to timestamp to_timestamp (' 2015-07-16 4:00:05 ', ' yyyy-mm-ddhh24:mi:ss ');
--or use flashbackdatabase to SCN 947921
sql> ALTER DATABASE open;
Sql> select Open_mode from V$database;
Open_mode
--------------------
READ only
--Start real-time applications
sql> ALTER Database RECOVER MANAGED STANDBY database USING current LOGFILE DISCONNECT;
Sql> select Open_mode from V$database;
Open_mode
--------------------
READ only with APPLY
--Check the log to see that the log has been applied from the point of flash back
Thu Jul 16 13:36:01 2015
Flashback database to Timestampto_timestamp (' 2015-07-16 4:00:05 ', ' yyyy-mm-dd hh24:mi:ss ')
Flashback Restore Start
Thu Jul 16 13:39:30 2015
Flashback Restore Complete
Flashback Media Recovery Start
Started Logmerger process
Parallel Media Recovery Startedwith Slaves
Flashback Media Recovery log+fra/htdb5/archivelog/2015_07_16/thread_1_seq_180047.2212.885180637
Thu Jul 16 13:41:54 2015
Flashback Media Recovery log+fra/htdb5/archivelog/2015_07_16/thread_1_seq_180061.2611.885182343
Thu Jul 16 13:42:04 2015
Flashback Media Recovery log+fra/htdb5/archivelog/2015_07_16/thread_1_seq_180062.2861.885182537
Thu Jul 16 13:42:12 2015
Incomplete Recovery applieduntil change 71489772016 time 07/16/2015 04:00:06
Flashback Media Recoverycomplete
Completed:flashback databaseto timestamp to_timestamp (' 2015-07-16 4:00:05 ', ' yyyy-mm-dd hh24:mi:ss ')
Thu Jul 16 13:43:25 2015
Deleted Oracle Managed file+fra/htdb5/archivelog/2015_07_15/thread_1_seq_179690.2885.885083087
Thu Jul 16 13:43:25 2015
Standby Controlfile Consistentwith Primary
RFS[3]: Selected log 8 Forthread 1 sequence 180122 dbid 1083719948 branch 759079182
Archived Log Entry 180115 addedfor thread 1 sequence 180121 ID 0x40a48484 dest 1:
Thu Jul 16 13:45:41 2015
ALTER DATABASE Open
Data Guard brokerinitializing ...
Data Guard brokerinitialization Complete
Smon:enabling Cache Recovery
Dictionary Check Beginning
Dictionary Check Complete
Database Characterset ISZHS16GBK
No Resource Manager Plan Active
replication_dependency_trackingturned off (no async multimaster replication found)
Physical standby databaseopened for read only access.
Completed:alter Database Open
Thu Jul 16 13:45:44 2015
ALTER database RECOVER managedstandby database THROUGH all switchoverdisconnect USING current LOGFILE
Attempt to start backgroundmanaged Standby Recovery process (HTDB5)
Thu Jul 16 13:45:44 2015
MRP0 started with pid=51, osid=14743
Mrp0:background Managedstandby Recovery Process started (HTDB5)
Started Logmerger process
Thu Jul 16 13:45:50 2015
Managed Standby recoverystarting Real time Apply
Parallel Media Recovery Startedwith Slaves
Waiting for any non-currentorls to be archived ...
All Non-current Orls has beenarchived.
Media Recovery Log +fra/htdb5/archivelog/2015_07_16/thread_1_seq_180062.2861.885182537
Completed:alter databaserecover MANAGED STANDBY DATABASE throughall switchover DISCONNECT USING currentlogfile
Thu Jul 16 13:46:08 2015
Media Recovery log+fra/htdb5/archivelog/2015_07_16/thread_1_seq_180063.3683.885182777
Thu Jul 16 13:46:35 2015
Media Recovery log+fra/htdb5/archivelog/2015_07_16/thread_1_seq_180064.2542.885183119
Thu Jul 16 13:47:07 2015
Media Recovery log+fra/htdb5/archivelog/2015_07_16/thread_1_seq_180065.2717.885183615
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
Dataguard Standby ORA-01196 Failure Recovery A