Enrolling Protected Databases

This section explains how to enroll a protected database using either Cloud Control (recommended) or the DBMS_RA command-line interface.

To enroll a protected database on the Recovery Appliance with Cloud Control:

Using the Targets dropdown, select the Databases item.

This opens a screan for Databases.
From the table of Databases, select the database that is to be configured for backup and recovery protection. You may need to login as an administrator for that database.

This loads a screen with graphical information about the performance of the database, as well as subsequent drop-downs for Performance, Availability, Security, Schema, and Administration.
From the Availability drop-down for your chosen database, highlight Backup & Recovery and from its flyout select Configure Backup.
From the Configure Backup screen for your chosen database, select from the Destination drop-down the option Recovery Appliance.

For the Host Credentials field, search for a Named user who has database host credentials.
In the subsequent screen for Configure Backup for your chosen database:
- From the Recovery Appliance drop-down, select the destination recovery appliance.
- From the Virtual Private Catalog User drop-down, select the approriate VPC user.
- Establish other options for the database.
  
  If the protection policy has auto tune enabled, the reserved space does not need to be specified.
If the Recovery Appliance only supports TCP or TCPS-only, the Protocol cannot be changed. Only if the Recovery Appliance is in dual mode does the drop-down provide options for TCP and TCPS.

Enable Real-Time Redo switch is only permissible if the database is not a Data Guard database and if the database is in archive log mode.

The Wallet field shows the path to the wallet if it exists, and the field is disabled. If no wallet exists, you can provide a location or use the recommended location for the wallet.

For Oracle Databases prior to DB 23, the user can choose to Install Backup Module if it is needed.
When finished with the Configure Backup settings for your chosen database, Submit them.

To enroll a protected database on a Recovery Appliance with PL/SQL:

When enrolling databases using the DBMS_RA command-line interface, you must perform the following tasks:

Add protection database metadata to the Recovery Appliance using DBMS_RA
Grant database access to a Recovery Appliance account using DBMS_RA.
Configuring the protected database for access (see Zero Data Loss Recovery Appliance Protected Database Configuration Guide)

Add Metadata for the Database

For a database to be protected, you must add metadata for this database to the Recovery Appliance using DBMS_RA.ADD_DB. This procedure requires you to specify an existing protection policy and the amount of reserved space for the database.

You must log in to the Recovery Appliance with the RASYS account or with a named db_user with user_type=admin.

The following examples assumes the following requirements:

You want to make orcld a protected database.
You want to add this database to the existing bronze protection policy, and provide it with 200 GB of reserved space.

With SQL*Plus or SQL Developer, connect to the Recovery Appliance metadata database as RASYS.
Use the ADD_DB procedure to add database metadata to the Recovery Appliance and assign a protection policy.

For example, the following anonymous block adds database orcld:
```
BEGIN
  DBMS_RA.ADD_DB (
    db_unique_name         => 'orcld',
    protection_policy_name => 'bronze',
    reserved_space         => '200G');
END;
```

Optionally, query the recovery catalog to see information about the newly added database.

For example, execute the following query to show details about orcld (sample output included):

COLUMN PROT_DB FORMAT a10
COLUMN POLICY_NAME FORMAT a11
SELECT DB_UNIQUE_NAME AS PROT_DB, DB_KEY, DBID, POLICY_NAME
FROM   RA_DATABASE
WHERE  DB_UNIQUE_NAME = 'ORCLD';

PROT_DB        DB_KEY       DBID POLICY_NAME
---------- ---------- ---------- -----------
ORCLD             301 3210984255 BRONZE

Note:

In an Oracle Data Guard environment, add the db_unique_name of whichever database (primary or standby) that you registered with the Recovery Appliance catalog.

See Also:

"ADD_DB"

Granting Access

You must grant the necessary privileges to a Recovery Appliance user account—which is also a virtual private catalog account—so that protected databases that authenticate with this account can perform backup and restore operations. The DBMS_RA.GRANT_DB_ACCESS procedure associates a protected database with a virtual private catalog.

You must log in to the Recovery Appliance with the RASYS account or with a named db_user with user_type=admin..
The the Recovery Appliance user account specified in DBMS_RA.GRANT_DB_ACCESS must exist.
You must have already added the protected database named orcld.

For this example, assume that you want to enable RMAN to CONNECT CATALOG as ravpc1 when backing up protected database orcld.

With SQL*Plus or SQL Developer, connect to the Recovery Appliance database as RASYS.
Run the GRANT_DB_ACCESS procedure to grant backup and restore privileges on the database for the user.

The following PL/SQL anonymous block grants access to protected database orcld to virtual private catalog account ravpc1:
```
BEGIN
   DBMS_RA.GRANT_DB_ACCESS (
     db_unique_name =>  'orcld',
     username       =>  'ravpc1');
END;
```

Optionally, query the recovery catalog to see information about the database access.

For example, execute the following query to show details about orcld and catalog owner ravpc1 (sample output included):

COLUMN PROT_DB FORMAT a10
COLUMN POLICY_NAME FORMAT a11
COLUMN USERNAME FORMAT a15
COLUMN DB_KEY FORMAT 999999
SELECT d.DB_UNIQUE_NAME AS PROT_DB, d.DB_KEY, 
       d.DBID, d.POLICY_NAME, a.USERNAME
FROM   RA_DATABASE d, RA_DB_ACCESS a 
WHERE  d.DB_UNIQUE_NAME = 'ORCLD'
AND    a.DB_KEY = d.DB_KEY;
 
PROT_DB     DB_KEY       DBID POLICY_NAME USERNAME
---------- ------- ---------- ----------- ---------------
ORCLD          301 3210984255 BRONZE      RAVPC1

Send the virtual private catalog user name and password to the DBA for each protected database that must authenticate using this account.
To complete the enrollment procedure, see Zero Data Loss Recovery Appliance Protected Database Configuration Guide.