Re: The Redo Hasn't Arrived Yet

From: Hemant K Chitale <hemantkchitale_at_gmail.com>
Date: Mon, 18 May 2020 22:37:32 +0800
Message-ID: <CAMNBsZt+zoiXgizLh7_33wJkxgW=vjB7CT=XoMt-qCmRx8ctSQ_at_mail.gmail.com>



Why ABORT for the Standby ?

I use SHUTDOWN IMMEDIATE.

Hemant K Chitale

On Mon, 18 May 2020, 22:11 Charlotte Hammond, <dmarc-noreply_at_freelists.org> wrote:

> Hello,
>
> 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
>
>
> Mon May 18 07:03:53 2020
> Standby crash recovery failed to bring standby database to a consistent
> point because needed redo hasn't arrived yet.
> MRP: Wait timeout: thread 1 sequence# 0
> Standby 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 unavailable
> Recovery interrupted!
> Some recovered datafiles maybe left media fuzzy
> Media recovery may continue but open resetlogs may fail
> Completed Standby Crash Recovery.
> Errors in file
> /u01/app/oracle/diag/rdbms/dinmybs1/DINMYBS1/trace/DINMYBS1_ora_4660.trc:
> ORA-10458: standby database requires recovery
> ORA-01196: file 1 is inconsistent due to a failed media recovery session
> ORA-01110: data file 1: '+DATA/dinmybs1/datafile/system.268.1023746733'
> ORA-10458 signalled during: ALTER DATABASE OPEN /* db agent *//* {0:0:2}
> */...
>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Mon May 18 2020 - 16:37:32 CEST

Original text of this message