Databases Reference
In-Depth Information
To recompile all PL/SQL modules, run utlirp.sql and utlrp.sql on the target platform
To change the internal database identifier, use DBNEWID Utility
Finished conversion at source at 25-NOV-12
RMAN>
7.
Once the
convert database
command completes its execution, open the source database
read/write.
SQL> alter database open read write;
8.
The conversion process creates files in the directory you specified with the
transport
script and the
db_file_name_convert
parameters. Copy these files, including the
transportscript.sql
file, to a location on the destination server.
9.
Edit the
transportscript.sql
file so the file reflects the correct data file locations on the
destination server.
10.
The
transportscript.sql
file contains a pfile for the database you'll be transporting to
the destination server. In our case, the name of the pfile is listed toward the end of the
transportscript.sql
file as follows:
PFILE='/u01/app/oracle/product/12.1.0/db_1/dbs/init_00nolft7_1_0.ora'
The pfile in the
transportscript.sql
file has several initialization parameters, grouped under the following sections:
# Please change the values of the following parameters:
# Please review the values of the following parameters:
# The values of the following parameters are from source database:
Obviously, you must review the parameters carefully and change any parameters that you must, including the
names of the control files as well as the value of the
db_name
initialization parameter for the new database. You must
also, at this point, if necessary, change any of the converted data files as well as any memory settings for the new
database.
11.
Go to the destination server and connect to the destination database as shown here.
SQL> connect / as sysbackup
12.
Create the new database on the destination server by executing the script
transport.sql
that
the
convert database
command has created for you.
SQL> @transportscript
Once the script
transport.sql
completes executing, your new duplicate database is ready for you.
How It Works
A major requirement for performing a cross-platform database transport is that the source and destination operating
systems must have the same endian format. That is, both endian formats must be either little-endian or big-endian.
You can't transport an entire database using RMAN image copies (or backup sets) if the endian formats of the source
and destination servers don't match.
