Documente Academic
Documente Profesional
Documente Cultură
Follow this step-by-step procedure to roll forward a physical standby database that has fallen far
behind the primary database.
Note: The steps in this section can also be used to resolve problems if a physical standby database
has lost or corrupted archived redo data or has an unresolveable archive gap.
select 'backup incremental from scn '||current_scn||' database format
"/backup/oracle/PWHRMN20/rman/INC_FOR_STANDBY_%U.bkp";' from v$database;
1. On the standby database, query the V$DATABASE view and record the current SCN of the
standby database:
SQL> SELECT CURRENT_SCN FROM V$DATABASE; CURRENT_SCN -----------
233995
data:text/html;charset=utf-8,%3Cheader%20style%3D%22display%3A%20block%3B%20color%3A%20rgb(102%2C%20102%2C%20102)%3B%20font-family%
1/2
3/15/2015
You must create this incremental backup on disk for it to be useful. When you move the
incremental backup to the standby database, you must catalog it at the standby as described in
Oracle Database Backup and Recovery Advanced User's Guide. Backups on tape cannot be
cataloged.
4. Transfer all backup sets created on the primary system to the standby system (note that there
may be more than one backup file created):
SCP /tmp/ForStandby_* standby:/tmp
5. Connect to the standby database as the RMAN target, and catalog all incremental backup
pieces:
RMAN> CATALOG START WITH '/tmp/ForStandby_';
6. Connect to the standby database as the RMAN target and apply incremental backups
RMAN> RECOVER DATABASE NOREDO;
7. Remove the incremental backups from the standby system:
RMAN> DELETE BACKUP TAG 'FOR STANDBY';
8. Manually remove the incremental backups from the primary system:
rm /tmp/ForStandby_*
9. Start Redo Apply on the physical standby database:
data:text/html;charset=utf-8,%3Cheader%20style%3D%22display%3A%20block%3B%20color%3A%20rgb(102%2C%20102%2C%20102)%3B%20font-family%
2/2