1 StartingRedoApplyTostartapplyservicesonaphysicalstandbydatabase, ensurethephysicalstandbydatabaseisstartedandmountedandthenstartRedoApplyusingtheSQLALTERDATABASERECOVERMANAGEDSTANDBYDATABASEst atement. You
1 Starting Redo Apply To start apply services on a physical standby database, ensure thephysical standby database is started and mounted and then start Redo Applyusing the SQL ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement. You
1 Starting Redo Apply
To start apply services on a physical standby database, ensure thephysical standby database is started and mounted and then start Redo Applyusing the SQL ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement.
You can specify that Redo Apply runs as a foreground session or as abackground process, and enable it with real-time apply.
- To start Redo Apply in the foreground, issue the following SQL statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;
- If you start a foreground session, control is not returned to the command prompt until recovery is canceled by another session.
- To start Redo Apply in the background, include the DISCONNECT keyword on the SQL statement. For example:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
Alterdatabase recover managed standby database disconnect from session;
- This statement starts a detached server process and immediately returns control to the user. while the managed recovery process is refreshing recovery in the background, the foreground process that issued the RECOVER statement can continue other Ming other tasks. this does not disconnect the current SQL session.
- To start real-time apply, include the using current logfile clause on the SQL statement. For example:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE;
Alterdatabase recover managed standby database using current logfile disconnect fromsession;
2 Stopping Redo Apply
To stop Redo Apply, issue the following SQL statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
3 Advanced Configuration
3.1 Using Real-Time Apply to ApplyRedo Data Immediately
If the real-time apply feature is enabled, apply services can applyredo data as it is stored ed, without waiting for the current standby redo logfile to be archived. this results in faster switchover and failover timesbecause the standby redo log files have been applied already to the standbydatabase by the time the failover or switchover begins.
Use the alter database statement to enable the real-time applyfeature, as follows:
- For physical standby databases, issue the alter database recover managed standby database using current logfile statement.
- For logical standby databases, issue the alter database start logical standby apply immediate statement.
Real-time apply requires a standbydatabase that is configured with a standby redo log and that is in ARCHIVELOGmode.
The figure belowshowsa Data Guard configuration with a local destination and a standby destination. as the remote file server (RFS) process writes the redo data to standby redolog files on the standby database, apply services can recover redo from standbyredo log files as they are being filled.
3.2 Specifying a Time Delay for theApplication of Archived Redo Log Files
In some cases, you may want to create a time lag between the timewhen redo data is stored ed from the primary site and when it is applied to thestandby database. you can specify a time interval (in minutes) to protectagainst the application of specified upted or erroneous data to the standby database. when you set a DELAY interval, it does not delay the transport of the redo datato the standby database. instead, the time lag you specify begins when the redodata is completely archived at the standby destination.
Note:
If you define a delay for a destination that has real-time applyenabled, the delay is ignored.
Specifying a Time Delay
You can set a time delay on primary and standby databases using theDELAY = minutes attribute of theLOG_ARCHIVE_DEST_n initializationparameter to delay applying archived redo log files to the standby database. bydefault, there is no time delay. if you specify the DELAY attribute withoutspecifying a value, then the default delay interval is 30 minutes.
Canceling a Time Delay
You can cancel a specified delay interval as follows:
- For physical standby databases, use the NODELAY keyword of the recover managed standby database clause:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
- For logical standby databases, specify the following SQL statement:
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
These commands result in apply services immediately beginning toapply archived redo log files to the standby database, before the time intervalexpires.
Using Flashback Database as anAlternative to Setting a Time Delay
As an alternative to setting an apply delay, you can use FlashbackDatabase to recover from the application of specified upted or erroneous data to thestandby database. flashback Database can be quickly and easily flash back astandby database to an arbitrary point in time.
Author: xiangsir
QQ: 444367417
MSN: xiangsir@hotmail.com