Database Reference
In-Depth Information
3.
Create a user that will own the tables and other objects used to store the target database
metadata. I recommend giving the recovery catalog user a name such as RCAT so that
it's readily identifiable as the user that owns the recovery catalog objects. Also, grant the
RECOVERY_CATALOG_OWNER role to the RCAT user as well as CREATE SESSION :
CREATE USER rcat IDENTIFIED BY foo
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE reccat
QUOTA UNLIMITED ON reccat;
--
GRANT RECOVERY_CATALOG_OWNER TO rcat;
GRANT CREATE SESSION TO rcat;
Connect through RMAN as RCAT , and create the recovery catalog objects:
4.
$ rman catalog rcat/foo
Now, run the CREATE CATALOG command:
5.
RMAN> create catalog;
RMAN> exit;
6.
This command may take a few minutes to run. When it's finished, you can verify that the
tables were created with the following query:
$ sqlplus rcat/foo
SQL> select table_name from user_tables;
7.
Here is a small sample of the output:
TABLE_NAME
------------------------------
DB
NODE
CONF
DBINC
Registering a Target Database
Now, you can register a target database with the recovery catalog. Log in to the target database server. Ensure that you
can establish Oracle Net connectivity to the recovery catalog database. For instance, one approach is to populate the
TNS_ADMIN/tnsnames.ora file with an entry that points to the remote database. On the target database server, register
the recovery catalog, as follows:
$ rman target / catalog rcat/foo@rcat
When you connect, you should see verification that you're connecting to both the target and the recovery catalog:
connected to target database: O12C (DBID=3423216220)
connected to recovery catalog database
 
Search WWH ::




Custom Search