[Oracledatagard] recovery from database ORA-16032: parameterORA-07286: Problem

The data center is powered off, so oracle's slave database must be restarted:

1. log on to sqlplus and start it. An error message is displayed:

SQL> STARTUP MOUNT;

ORA-16032: parameter LOG_ARCHIVE_DEST_3 destination string cannot be translated

2. Check the specific path of LOG_ARCHIVE_DEST_3.

[Root @ localhost ~] # Su-oracle
-Rw-r -----. 1 oracle dba 5632 September August 30 2013 spfilepowerdes. ora

3 # path found

[Oracle @ localhost dbs] $ strings spfile *. ora | grep dest_3

4. check the path and troubleshoot the problem.

5. Solve the Problem

/Data already exists, but cannot be used. google, see two solutions

6. log on to the sqlplus start slave database again

SQL> STARTUP MOUNT; ORACLE instance started. total System Global Area 5344731136 bytesFixed Size 2213136 bytesVariable Size 3489663728 bytesDatabase Buffers 1811939328 bytesRedo Buffers 40914944 bytesDatabase mounted. SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; Database altered. SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE; ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE * ERROR at line 1: ORA-01153: an incompatible media recovery is activeSQL> alter database open; alter database open * ERROR at line 1: ORA-10456: cannot open standby database; media recovery session may be inprogressSQL> recover managed standby database cancel; Media recovery complete.7 attempt to automatically recover, but still fail, as long as you stop SQL> recover automation standby database; ORA-00279: change 10386441904 generated at 04/18/2014 17:56:46 needed forthread 1ORA-00289: suggestion:/data/oracle/oradgdata/standby_archive/category: change 10386441904 for thread 1 is in sequence #7368ORA-00278: log file '/data/oracle/oradgdata/standby_archive/rj71__821708334.dbf' no longer neededfor this recoveryORA-00308: cannot open archived log '/data/oracle/oradgdata/standby_archive/4107316_821708334.dbf 'ora-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3 Specify log: {<RET> = suggested | filename | AUTO | CANCEL} ORA-00308: cannot open archived log '/data/oracle/oradgdata/standby_archive/%7%_821708334.dbf 'ora-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3SQL> recover managed standby database disconnect from session; Media recovery complete.

8. Check the status of the currently deployed ard.

SQL> SELECT MESSAGE FROM V$DATAGUARD_STATUS;MESSAGE--------------------------------------------------------------------------------ARC0: Archival startedARC1: Archival startedARC2: Archival startedARC3: Archival startedARC4: Archival startedARC5: Archival startedARC6: Archival startedARC7: Archival startedARC8: Archival startedARC9: Archival startedARCa: Archival startedMESSAGE--------------------------------------------------------------------------------ARCb: Archival startedARCc: Archival startedARCd: Archival startedARCe: Archival startedARCf: Archival startedARCg: Archival startedARCh: Archival startedARCi: Archival startedARC1: Becoming the 'no FAL' ARCHARC2: Becoming the heartbeat ARCHARCj: Archival startedMESSAGE--------------------------------------------------------------------------------Media Recovery Start: Managed Standby RecoveryManaged Standby Recovery not using Real Time ApplyMedia Recovery Waiting for thread 1 sequence 7368Fetching gap sequence in thread 1, gap sequence 7368-7392FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 7368-7392 DBID 3391761643 branch 821708334FAL[client]: All defined FAL servers have been attempted.Attempt to start background Managed Standby Recovery processMRP0: Background Managed Standby Recovery process startedManaged Standby Recovery not using Real Time ApplyMESSAGE--------------------------------------------------------------------------------Media Recovery Waiting for thread 1 sequence 7368Fetching gap sequence in thread 1, gap sequence 7368-7392FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 7368-7392 DBID 3391761643 branch 821708334FAL[client]: All defined FAL servers have been attempted.MRP0: Background Media Recovery cancelled with status 16037MRP0: Background Media Recovery process shutdownManaged Standby Recovery CanceledManaged Standby Recovery not using Real Time ApplyAttempt to start background Managed Standby Recovery processMESSAGE--------------------------------------------------------------------------------MRP0: Background Managed Standby Recovery process startedManaged Standby Recovery not using Real Time ApplyMedia Recovery Waiting for thread 1 sequence 7368Fetching gap sequence in thread 1, gap sequence 7368-7392FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 7368-7392 DBID 3391761643 branch 821708334FAL[client]: All defined FAL servers have been attempted.52 rows selected.

9. Try to directly change the status to open.

SQL> alter database open; Database altered. SQL> select open_mode from v $ database; OPEN_MODE--------------------READ ONLY # Place slave database in auto recovery status SQL> recover managed standby database disconnect from session; Media recovery complete.

10 # check, check the archiving logs of the master and slave nodes

SQL> archive log list;                                                                                                                                                                         Database log mode       Archive ModeAutomatic archival       EnabledArchive destination       /oracle/app/oracle/flash_recovery_area/archivelogOldest online log sequence     7777Next log sequence to archive   7779Current log sequence       7779SQL>   

# Slave database status:

SQL>  archive log list;                                                                                                                                                                        Database log mode       Archive ModeAutomatic archival       EnabledArchive destination       /data/oracle/oradgdata/standby_archiveOldest online log sequence     7778Next log sequence to archive   0Current log sequence       7779SQL> 

Finally, I asked the cat and cat how to thoroughly check the consistency between the master and slave data of the ARD, and the results were reviewed by the cat and the beauty of the cat. Read more about the official documents of datagard. Don't always ask her, you have to study and summarize it yourself.

Haha, it seems that it is time to make up for oracle datagard.