PowerView is On Support Identifier: 19549137 (Capgemini Se...

Rikesh (Available) (3) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates

Document Display Give Feedback...

Search: rman catalog

[1548952.2]
Why use a recovery catalog? Platform as a Service (PaaS)
and Oracle Cloud
The RMAN catalog has several benefits. It makes restore if all the target database is lost, including the controlfile. As that Infrastructure (OCI)
controlfile contains all backup information, the catalog would then be used to identify a controlfile backup. If an RMAN Information Center
[2048297.2]
catalog is not used, the controlfile autobackup should be configured to ON. There are some features which are only
supported using an RMAN catalog. Primarily the ability to store scripts which would be available to all target databases
using the catalog.
Document References
It is recommended that the RMAN recovery catalog schema be created in a database which would be available if the target
database is lost. It is not recommended to create the recovery catalog in the target database itself. Ideally, the catalog is
Recently Viewed
created in a database on a different server. If it is not possible to create the recovery catalog on a different server, ensure
that the recovery catalog and target databases do not reside on the same disks. You do not want a failure to affect both Troubleshooting I/O
the recovery catalog and the target database. Therefore, if possible, take other measures as well to eliminate common Related Waits [223117.1]
points of failure between your recovery catalog database and the target databases using the catalog. Script To Monitor Memory
Usage By Database
The recovery catalog contains information about RMAN operations, including: Sessions [239846.1]
Understanding and Tuning
+ Datafile and archived redo log backup sets and backup pieces Buffer Cache and DBWR
[62172.1]
+ Datafile copies
+ Archived redo logs and their copies Listener Hang , Lsnrctl

+ Tablespaces and datafiles on the target database Slow Response , Tnsping

+ Stored scripts, which are named user-created sequences of RMAN commands Slow, Sqlplus remote
connections fails
+ Persistent RMAN configuration settings [2305554.1]
Creating a recovery catalog is a 3 step process. The recovery catalog is stored in the default tablespace of the recovery catalog Receiving An Error ORA-
owner/schema. SYS cannot be the owner of the recovery catalog. 16765: Redo Apply Is
Running [2188168.1]
1. Creating the recovery catalog owner/schema Show More
2. Creating the recovery catalog
3. Registering the target database(s)

1. Creating the Recovery Catalog Owner/Schema

1.1 Determine the size of recovery catalog schema :

Size of recovery catalog schema depends on

a) The number of databases monitored by the catalog.

b) The rate at which archived redo log generates in the target database

c) The number of backups for each target database

d) RMAN stored scripts stored in the catalog

1.2 Creating the recovery catalog schema:

Start by creating a database schema (usually called rman). Assign an appropriate tablespace to it and grant it the
recovery_catalog_owner role. For example:

% sqlplus '/ as sysdba'

SQL> CREATE USER <catalog username> IDENTIFIED BY <password>

DEFAULT TABLESPACE tools
TEMPORARY TABLESPACE temp
QUOTA UNLIMITED ON tools;

SQL> GRANT CONNECT, RECOVERY_CATALOG_OWNER TO <username>;

2. Creating the Recovery Catalog

Using RMAN, connect to the recovery catalog schema and create the catalog schema. For example:

In the below example "<catalog db connect string> " is the catalog database connection string. Before creating the
recovery catalog make sure to have the tnsnames.ora entry for the catalog database in the target server and the listener
must be up and running in the catalog database server. You must be able to connect to the catalog database from
sqlplus from the target server

Copyright (c) 2019, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement