Detailed process of fixing Oracle11GDataGuardORA-16086 Problems
1. Problem description: No redo logs are applied to the standby slave database.
Tue JUNl 22 09:05:07 2014
2. View redo log information in the slave Database
SQL> show parameter log_file_name_convert;
3. redo log Reconstruction
Check the current redo log status.
4. Check whether the archive file is complete.
If the slave database redo log is damaged, it can be repaired as long as the archive log of the slave database is in place, and Standy does not need to be re-executed.
5. Check whether the archived logs are written to the slave database:
Therefore, the lgwr process is used to transmit logs using the lgwr process. In other modes, logs are transmitted using arch when logs are written to the archive process, you have not recently changed the slave database protection mode.
6. Check alert information
Because oracle archive logs exist in the master database at, go to the master database to view the alert Log information from the database:
7. perform operations on the slave database to restore the logfile group of yesterday:
Stop the redo application first
8. Try to shut down and restart the slave database.
Shutdown immediate;
- Tue JUNl 22 11:04:42 2014
MRP0: Background Media Recovery canceled with status 16037
Errors in file/oracle/app/oracle/diag/rdbms/pddgunq/powerdes/trace/powerdes_pr00_13338.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery
Errors in file/oracle/app/oracle/diag/rdbms/pddgunq/powerdes/trace/powerdes_pr00_13338.trc:
ORA-16037: user requested cancel of managed recovery operation
Waiting for MRP0 pid 13335 to terminate
Tue JUNl 22 11:04:44 2014
MRP0: Background Media Recovery process shutdown (powerdes)
License high water mark = 40
ALTER DATABASE CLOSE NORMAL
Tue JUNl 22 11:04:45 2014
SMON: disabling cache recovery
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Tue JUNl 22 11:04:46 2014
ARCH shutting down
Tue JUNl 22 11:04:46 2014
ARCH shutting down
Tue JUNl 22 11:04:46 2014
ARCj: Archival stoppedTue Jul 22 11:04:46 2014
ARCH shutting downue Jul 22 11:04:46 2014
ARCH shutting down
ARCH shutting down
Tue JUNl 22 11:04:46 2014
ARCH shutting downARCi: Archival stopped
Tue JUNl 22 11:04:46 2014
ARCH shutting down
Tue JUNl 22 11:04:46 2014
ARCH shutting down
ARCf: Archival stopped
ARCg: Archival stoppedARCh: Archival stopped
Tue JUNl 22 11:04:46 2014
ARCH shutting downARCe: Archival stopped
Tue JUNl 22 11:04:46 2014
ARCH shutting downue Jul 22 11:04:46 2014
ARCd: Archival stopped
ARCH shutting downue Jul 22 11:04:46 2014
ARCc: Archival stoppedTue Jul 22 11:04:46 2014
ARCH shutting downARCH shutting down
Tue JUNl 22 11:04:46 2014
Tue JUNl 22 11:04:46 2014
Tue JUNl 22 11:04:46 2014
ARCH shutting downue Jul 22 11:04:46 2014
ARCH shutting down
ARCH shutting downARCa: Archival stopped
ARC9: Archival stopped
ARCH shutting down
ARC7: Archival stopped
ARCb: Archival stopped
ARC6: Archival stoppedARC5: Archival stoppedTue Jul 22 11:04:46 2014
ARCH shutting downARC8: Archival stopped
ARC4: Archival stopped
ARC2: Archival stopped
ARC3: Archival stopped
Tue JUNl 22 11:04:46 2014
ARCH shutting down
ARC1: Archival stoppedTue Jul 22 11:04:46 2014
ARCH shutting down
ARC0: Archival stopped
Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Tue JUNl 22 11:04:48 2014
Stopping background process VKTM:
Tue JUNl 22 11:04:50 2014
Instance shutdown complete restart slave Database
9. restore archived logs from the database. This process is slow and takes a long time.
Recover automatic standby database;
10. Two operations are summarized:
First, redo log is rebuilt and three groups of standby logs are added:
