Databases Reference
In-Depth Information
2.
RMAN starts an auxiliary instance in nomount mode first. You don't have to specify a
parameter file for this auxiliary instance, since RMAN automatically creates the file. The
name of the auxiliary instance is also made up by RMAN, as shown here:
Creating automatic instance, with SID='nFya'
3.
RMAN restores a backup of the target database control file and uses it to mount the
auxiliary database.
Using the
switch
operation, RMAN restores all data files from the target database for
the auxiliary instance. These files are restored to the location specified by the
auxiliary
destination
clause in the
transport tablespace
command.
4.
5.
RMAN also stores the files pertaining to the tablespaces in the transportable tablespace set
in the location you specify with the
tablespace destination
parameter in the
transport
tablespace
command.
6.
Once the data files from the target database are all restored to the auxiliary database
location, RMAN performs a point-in-time recovery of the auxiliary instance. In our
example, since we didn't specify a target time, a complete database recovery is performed.
Note that all applicable archived redo logs are also automatically restored and applied
by RMAN during the recovery process. Once the recovery is finished, an open resetlogs
operation is performed on the auxiliary database by RMAN.
7.
RMAN invokes the Data Pump Export utility (in the transportable tablespace mode) to
create the export dump file containing the tablespaces in the transportable tablespace set.
By default, the export dump file is placed in the location you specify with the
tablespace
destination
clause of the
transport tablespace
command.
8.
RMAN also simultaneously generates a Data Pump import script you can use to plug in the
transported tablespaces into the target database. The default script name is
impscrpt.sql
,
and this script is located in the directory specified by the
tablespace destination
clause
of the
transport tablespace
command.
9.
RMAN shuts down the auxiliary instance and automatically deletes all the files created
and used during the transport tablespace process. The only files that remain are the
transportable set files, the Data Pump export log, and the sample Data Pump import
script.
In the example shown in the solution, the RMAN-created
impscrpt.sql
script was used to import the tablespaces
into the target database. The script utilizes a PL/SQL script to import the tablespaces.
Alternatively, you can use the following Data Pump import command to import the tablespaces. For example:
$ impdp sys/sammyy1
directory=exp_data_dir
dumpfile= 'dmpfile.dmp'
transport_datafiles= /u05/app/oracle/transportdest/test2_01.dbf
■
You can also use non-rMan backups to create transportable tablespace sets, as long as you record the data
file copies and archived redo logs in the rMan repository using the
catalog
command.
Note
