A detailed explanation of the recovery database of Rman heterogeneous machine

Experimental environment:

Source database server Name: Our database global name and SID:ORCL

Target database server name: Beijing only database software, no new database

1. The source database backs up the data and copies it to the target database server

\\192.168.2.7 \E$\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORCL. ORA

Copied to

E:\app\Administrator\product\11.2.0\dbhome_1\database

2. Create service services on target database

Oradim-new-sid ORCL

3. Using the source database SPFile generation Pfile

The source database's

App\administrator\product\11.2.0\dbhome_1 \DATABASE\SPFILEORCL. ORA

Copy to target database

E:\app\Administrator\product\11.2.0\dbhome_1 \DATABASE\SPFILEORCL. ORA

sql> create pfile= ' E:\backup\pfile_orcl.ora ' from SPFile;

The file has been created.

4. Modify the configuration file if the source data and the target database directory structure are inconsistent

E:\backup\pfile_orcl.ora

Here the target database is simply installed with Oracle software and there is no new Oracle database, so a new directory is required to guarantee and

The directory set in the Pfile file is consistent.

mkdir E:\APP\ADMINISTRATOR\ADMIN\ORCL

mkdir E:\app\Administrator\admin\orcl\adump

mkdir E:\app\Administrator\admin\orcl\dpdump

mkdir E:\app\Administrator\admin\orcl\pfile

mkdir E:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL

mkdir E:\APP\ADMINISTRATOR\ORADATA\ORCL

mkdir E:\backup\archivelog

5. Build SPFile on the target database according to the modified Pfile

Sql>create spfile from pfile= ' E:\backup\pfile_orcl.ora ';

6. Target database boot to Nomount state

sql> startup Nomount;

The ORACLE routine has started.

Total System Global area 1185853440 bytes

Fixed Size 2175168 bytes

Variable Size 352325440 bytes

Database buffers 822083584 bytes

Redo buffers 9269248 bytes