Databases Reference
In-Depth Information
RMAN> restore foreign tablespace demo
2> format '/u01/app/oracle/oradata/orcl1'
3> from backupset '/u02/app/oracle/oradata/transport_aknoqnt8'
4> dump file from backupset '/u02/app/oracle/oradata/export/trans_ts_alnoqntd_1_1';
Starting restore at 27-NOV-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring all files in foreign tablespace DEMO
channel ORA_DISK_1: reading from backup piece /u02/app/oracle/oradata/transport_aknoqnt8
channel ORA_DISK_1: restoring foreign file 10 to /u01/app/oracle/oradata/orcl1
channel ORA_DISK_1: foreign piece handle=/u02/app/oracle/oradata/transport_aknoqnt8
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring Data Pump dump file to
/u01/app/oracle/product/12.1.0/db_1/dbs/backup_tts_ORCL1_91741.dmp
channel ORA_DISK_1: reading from backup piece /u02/app/oracle/oradata/export/trans_ts_alnoqntd_1_1
channel ORA_DISK_1: foreign piece handle=/u02/app/oracle/oradata/export/trans_ts_alnoqntd_1_1
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Performing import of metadata...
IMPDP> Master table "SYSBACKUP"."TSPITR_IMP_ORCL1_ntuf" successfully loaded/unloaded
IMPDP> Starting "SYSBACKUP"."TSPITR_IMP_ORCL1_ntuf":
IMPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
IMPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
IMPDP> Job "SYSBACKUP"."TSPITR_IMP_ORCL1_ntuf" successfully completed at
Sat Nov 27 17:42:42 2012 elapsed 0 00:00:24
Import completed
Finished restore at 27-NOV-12
RMAN>
How It Works
When you're transporting tablespaces using RMAN backup sets, the terms
foreign data file
and
foreign tablespace
refer, respectively, to the source database data files and tablespaces that you're transporting and plugging into the
destination database. A
datapump destination
is the location on the target database's host server where you're storing
the Data Pump-related files, including the Data Pump export dump file and the log files.
The source and destination databases can be running on different platforms that use different endian formats.
If the endian formats on the two platforms are different, you must first convert the data. How this conversion is
performed depends on the clause you specify with the
backup
command. The
backup
command during a cross-platform
transport can contain either the
for transport
or the
to platform
clause. If you specify the
for transport
clause,
you can transport the backup set to any destination database and the endian format conversion will be done on the
destination server. If you specify the
to platform
clause, RMAN performs the endian format conversion on the source
database itself. In the example we showed in the Solution section, we chose to specify the
to platform
clause.
