The Redo Hasn't Arrived Yet
Date: Mon, 18 May 2020 14:09:45 +0000 (UTC)
Message-ID: <691766356.820137.1589810985809_at_mail.yahoo.com>
Hello,
Mon May 18 07:03:53 2020Standby crash recovery failed to bring standby database to a consistentpoint because needed redo hasn't arrived yet.MRP: Wait timeout: thread 1 sequence# 0Standby Crash Recovery aborted due to error 16016.Errors in file /u01/app/oracle/diag/rdbms/dinmybs1/DINMYBS1/trace/DINMYBS1_ora_4660.trc:ORA-16016: archived log for thread 1 sequence# 1134 unavailableRecovery interrupted!Some recovered datafiles maybe left media fuzzyMedia recovery may continue but open resetlogs may failCompleted Standby Crash Recovery.Errors in file /u01/app/oracle/diag/rdbms/dinmybs1/DINMYBS1/trace/DINMYBS1_ora_4660.trc:ORA-10458: standby database requires recoveryORA-01196: file 1 is inconsistent due to a failed media recovery sessionORA-01110: data file 1: '+DATA/dinmybs1/datafile/system.268.1023746733'ORA-10458 signalled during: ALTER DATABASE OPEN /* db agent *//* {0:0:2} */...
If we shutdown *abort* our Data Guard standbys (11.2.0.4 maximum performance with RTA), we occasionally get the errors below on restart ("redo hasn't arrived yet")
Now this isn't a problem and is easy to fix - but I'm trying to understand WHY it happens: How can the controlfile and/or datafile headers in the standby database be ahead of the available redo at the time of abort?i.e. What is different about crash recovery on a standby compared to a primary?
Many thanks for any clarifications!
Charlotte
--
http://www.freelists.org/webpage/oracle-l
Received on Mon May 18 2020 - 16:09:45 CEST