Oracle Database migration to a remote Data Protector cell--Best practices

37
CTXSYS SYSAUX
ANONYMOUS SYSAUX
MDDATA USERS
TSMSYS USERS
DIP USERS
SCOTT USERS
SQL> create user rmani identified by xxx default tablespace RCVCAT;
User created.
SQL> grant RECOVERY_CATALOG_OWNER TO rmani;
Grant succeeded.
SQL> alter user rmani quota unlimited on RCVCAT;
User altered.
SQL> grant connect,resource to rmani;
Grant succeeded.
SQL> connect rmani/xxx
Connected.
SQL>
Once the new RMAN user (RMANI) is created, we can start the import of the Recovery Catalog in
their schema:
oracle@hpu015[RCVCAT]:/home/oracle$ imp userid=rmani/xxx@RCVCAT file=rcvcat.dmp
fromuser=rman \ touser=rmani
Import: Release 10.2.0.3.0 - Production on Wed Mar 19 11:50:21 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V10.02.01 via conventional path
…
oracle@hpu015[RCVCAT]:/home/oracle$ rman catalog rmani/xxx@RCVCAT
Recovery Manager: Release 10.2.0.3.0 - Production on Wed Mar 19 11:54:23 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to recovery catalog database
RMAN>
The Recovery catalog has been imported into our target system, hpu015, and is ready to be used.