Oracle's use of Rman for machine recovery test records

The purpose of this test is to export the Rman backup from the production database and then restore it in the test database

1, copy Backup to the appropriate directory

2, enter Rman

Rman target \

3. Close the database

Shutdown

4, start the database in Nomount mode

Startup Nomount

5, Recovery control file

Restore Controlfile from '/home/oracle/rman_backup/cf_c-1383295282-20171102-00 ';

6. Mount Database

ALTER DATABASE Mount;

7, set catalog path

Catalog start with '/home/oracle/rman_backup '

8, database Repair restore (media recovery)

Restore database;

In this step, the database corresponding to the physical file location has a DBF data file generated

9, Database recovery (recover)

Finally, this error is normal.

Because the hot backup we created is not a consistent backup, the source side of the archive is coming, but the online redo log file does not come with the backup set, The current state of the source is definitely not restored when this is restored. This error is prompted to continue recovery and requires thread 1 to generate a redo log of sequence 46037.

Files. We are only testing the process of recovering to a different machine, and we are not prepared to keep it exactly the same as the source-side database (if need be consistent, must be responsible for the source database side of the redo log files, it must first shutdown the source-side database line)

10, open the database in Resetlogs mode

ALTER DATABASE open resetlogs;

Detection

Select Max (Logno) from Blpos.postxnjnl;

Data Recovery test succeeded

Oracle's use of Rman for machine recovery test records