Shulou(Shulou.com)06/01 Report--

Dataguard lost the library archive because the archive deletion policy was not configured for the main database parameters.

Today, when I inspected the library, I found that the standby database was not started, and the monitoring agent was turned off. Start it manually.

Open the slave library (read_only) according to the logging convention, but the following error is displayed during open

Click (here) to collapse or open

Standby crash recovery failed to bring standby database to a consistentpoint because needed redo hasn't arrived yet.MRP: Wait timeout: thread 1 sequence# 173Standby Crash Recovery aborted due to error 16016.Errors in file / u01/app/oracle/diag/rdbms/orcl_st1/orcl/trace/orcl_ora_29639.trc:ORA-16016: archived log for thread 1 sequence# 173 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/orcl_st1/ Orcl/trace/orcl_ora_29639.trc:ORA-10458: standby database requires recoveryORA-01196: file 1 is inconsistent due to a failed media recovery sessionORA-01110: data file 1:'/ u01/app/oracle/oradata/orcl/system01.dbf'ORA-10458 signalled during: alter database open...

However, the manual application archive shows that the application has been completed, the background log database has been applied to sequence 173 and the main database has been applied to 214. looking under the archive directory, it is found that the archive has been lost, and the archive has not been sent because the standby machine is not turned off.

We restore archiving in the main library

Click (here) to collapse or open

Rman target / restore archivelog from sequence 173

Copy the recovered log to the standby database

Manually register the missing archive, which I handled in batches with a script

Click (here) to collapse or open

For i in `Archive 173214`; do echo "ALTER DATABASE REGISTER LOGFILE'/ u01max archivemax 1 _" $I "_ 956999399.dbftern'"; done173-214is the range of missing archives

Click (here) to collapse or open

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "173" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1' 174' 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "175" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1' 176' 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1' 177' 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 '178' 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1' 179' 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "180" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "181" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "182" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "183" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "184" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "185" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 '186' 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "187" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "188" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "189" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "190" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "191" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "192" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "1993" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "1944956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According ArchiveAccording to 195595 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccording to 196999999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccording to 1997 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccording to 1988956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1999 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccording to 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccording to 2018956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "202" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "203" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "204" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "205" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1' 206' 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "207" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "208" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 "209" 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccording to 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1 '211' 956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccording to 212956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccording to 213,956999399.dbf'

ALTER DATABASE REGISTER LOGFILE'/ u01According to ArchiveAccord 1' 2140956999399.dbf'

Click (here) to collapse or open

SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION

Note: if the amount of archiving is large, you can specify the degree of parallelism

Click (here) to collapse or open

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE PARALLEL 2 DISCONNECT FROM SESSION

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; database can be open normally.

Click (here) to collapse or open

SQL > ALTER DATABASE OPEN

SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION; finally set the main library archive deletion policy

Main library operation

Click (here) to collapse or open

Rman target / CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY; if the following error occurs

Click (here) to collapse or open

CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;new RMAN configuration parameters:CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;new RMAN configuration parameters are successfully storedRMAN-08591: WARNING: invalid archivelog deletion policy needs to modify the database parameters, restart the library, and then reset the archive deletion policy

Click (here) to collapse or open

SQL > alter system set "_ log_deletion_policy" = ALL scope=spfile sid='*'

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.