Databases Reference
In-Depth Information
You can also use the
transport tablespace
command to perform a tablespace transport to a past point in time.
Simply add the
until scn
clause to the
transport tablespace
command, as shown here:
RMAN> transport tablespace test1,test2
2> tablespace destination '/u05/app/oracle/transportdest'
3> auxiliary destination '/u05/app/oracle/auxdest'
4> until SCN 259386;
The preceding command will recover the transportable tablespaces only up to the specified SCN. Instead of the
SCN, you can also specify a target point in time or a restore point as well.
Performing a Cross-Platform Tablespace Transport by
Converting Files on the Source Host
Problem
You want to transport a set of tablespaces from a database running on a certain platform to a database running on
a different operating system. You're using RMAN image copies for the tablespace transport and you need to convert
files on the destination host for the transport of the tablespaces.
Solution
In this solution, we show you how to transport a set of two tablespaces—
users
and
example
—from a source database
named
orcl
running on a Linux host to a destination database named
orcl2
running on a Sun Solaris host. Here are
the steps to follow for transporting the tablespaces.
1.
Find the correct name for the destination operating system by querying the
V$TRANSPORTABLE_PLATFORM view in the source database.
. SQL> select platform_id,platform_name,endian_format
2 from v$transportable_platform
3* where upper(platform_name) like 'SOLARIS%';
PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT
----------- --------------------------------- ------------------
1 Solaris[tm] OE (32-bit) Big
2 Solaris[tm] OE (64-bit) Big
17 Solaris Operating System (x86) Little
20 Solaris Operating System (x86-64) Little
SQL>
From the query's output, you get the full name of the destination platform, which is “Solaris Operating
System (x86-64).”
2.
The next step is to place the two tablespaces you want to transport—
users
and
example
—
into read-only mode.
