Tchater maintenant avec le support
Tchattez avec un ingénieur du support

NetVault Plug-in for Oracle 12.3 - User Guide

Introducing Quest® NetVault® Backup Plug-in  for Oracle Defining a backup strategy Installing and removing the plug-in Configuring the plug-in Backing up data Using the Oracle Flashback Database Restoring data
Restoring and recovering data: an overview Performing User Managed restores Using advanced User Managed restore procedures Performing RMAN restores Using RMAN types of recovery in a non-RAC environment Using advanced procedures with RMAN restores
Maintaining the Recovery Catalog Using the RMAN CLI Using the plug-in with Oracle RAC Using the plug-in in a failover cluster environment Using the plug-in with Oracle Data Guard Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs) Troubleshooting

Creating the RMAN repository

As discussed in Choosing the location for the RMAN repository, for an RMAN backup strategy you must first choose a location for the RMAN repository. By default, this repository is maintained in the Control File. However, for larger or more mission-critical databases, create a Recovery Catalog database that can store a much longer history than the Control File.

Creating a Recovery Catalog is a three-step process: configure the database that will contain the Recovery Catalog, create the Recovery Catalog owner, and then create the Recovery Catalog itself.

Configuring the Recovery Catalog database

When you use a Recovery Catalog, RMAN requires that you maintain a Recovery Catalog schema. The Recovery Catalog is stored in the default tablespace of the schema. SYS cannot be the owner of the Recovery Catalog. Decide which database you want to use to install the Recovery Catalog schema. Quest recommends that you create a separate database for the Recovery Catalog and run the catalog database in ARCHIVELOG mode.

Next, allocate space to be used by the catalog schema. The size of the Recovery Catalog schema depends on the number of databases managed by the catalog. The schema also grows as the number of archived redo log files and backups for each database increases. For more information on sizing the Recovery Catalog schema, see Planning the Size of the Recovery Catalog Schema in the Oracle Database Backup and Recovery Advanced User’s Guide.

Creating the Recovery Catalog owner

After choosing the Recovery Catalog database and creating the necessary space, perform the following steps to create the owner of the Recovery Catalog and grant this user the necessary privileges:

1
Start SQL*Plus, and connect with administrator privileges to the database that will contain the Recovery Catalog.
sqlplus SYS/<password>@<connect_identifier> AS SYSDBA
3
Grant the RECOVERY_CATALOG_OWNER role to the schema owner.
4
Grant the CONNECT role to the rman user.

Creating the Recovery Catalog

After creating the catalog owner, create the catalog tables with the RMAN CREATE CATALOG command. This command creates the catalog in the default tablespace of the catalog owner.

> rman CONNECT CATALOG rman/<password>@<connect_identifier_for_catalog>
2
Run the CREATE CATALOG command to create the catalog.
CREATE CATALOG TABLESPACE <tablespace_name>;
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation