Databases Reference
In-Depth Information
1.
Connect to the source database through RMAN.
$ RMAN
RMAN> connect target sysbackup@orcl as sysbackup;
2.
Make the tablespace you want to transport read-only. In this case, the tablespace we want
to transport is named
demo
, so we set it to a read-only status.
RMAN> alter tablespace demo read only;
Statement processed
RMAN>
Select a method for naming the output files of the
backup
commmand. We chose to specify
the
format
clause of the RMAN
backup
command for this purpose. You can specify the
clause
to new
instead, to denote that you want RMAN to make sure that the restored
“foreign” data files use new OMF-format file names in the destination database. In our
backup
command in step 6, we use the
format
clause in the following manner:
3.
format '/u02/app/oracle/oradata/transport_%u'
4.
Find out the exact name of the destination platform with the following query:
RMAN> select platform_id, platform_name,endian_format
from v$transportable_platform
where upper(platform_name) like '%LINUX%';
The full name of the destination platform in our case is
Linux x86 64-bit
' This is what we'll specify in our RMAN
backup
command in step 6.
5.
Connect to RMAN with the source database as the target.
RMAN> connect target /
connected to target database: ORCL (DBID=1316762630)
RMAN>
Back up the source database tablespaces by specifying the
to platform
clause in the
RMAN
backup
command. You must also specify the
datapump
clause, so the export dump
file for the tablespace metadata is created as a separate backup piece.
6.
RMAN> backup to platform 'Linux x86 64-bit'
2> format '/u02/app/oracle/oradata/transport_%u'
3> datapump format '/u02/app/oracle/oradata/export/trans_ts_%U'
4> tablespace demo;
Starting backup at 27-NOV-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
Running TRANSPORT_SET_CHECK on specified tablespaces
TRANSPORT_SET_CHECK completed successfully
