Chat now with support
Chat with Support

NetVault Plug-in for Oracle 12.2 - 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

Querying CDB, PDB, and non-CDB databases

You can perform various queries of the databases by using SQL*Plus.

•
Determining whether a database is a CDB
•
Listing the containers in a CDB
•
Listing the PDBs and their status in a CDB
Determining whether a database is a CDB

The following is an example of the query and response for a non-CDB database:

SQLPLUS / AS SYSDBA
SQL> select name, cdb from v$database;
NAME CDB
--------- ---
PRODDB NO
SQL>

The following is an example of the query and response for a CDB database:

SQLPLUS / AS SYSDBA
SQL> select name, cdb from v$database;
NAME CDB
--------- ---
SALESDB YES
SQL>
Listing the containers in a CDB

You can list the containers in a CDB. For example:

SQL> column name format a20
SQL> select name, con_id, dbid, con_uid from v$containers order by con_id;
NAME CON_ID DBID CON_UID
-------------------- ---------- ---------- ----------
CDB$ROOT 1 3924627550 1
PDB$SEED 2 3283839514 3283839514
SALES_REGION200_PDB 3 3022227374 3022227374
SALES_REGION300_PDB 4 1471149548 1471149548
Listing the PDBs and their status in a CDB

You can list the PDBs and their status in a CDB. For example:

SQL> column pdb_name format a20
SQL> select pdb_id, pdb_name, status from dba_pdbs order by pdb_id;
PDB_ID PDB_NAME STATUS
---------- -------------------- ----------
2 PDB$SEED NORMAL
3 SALES_REGION200_PDB NORMAL
4 SALES_REGION300_PDB NORMAL

Restrictions for backing up and restoring a PDB

If you intend to target a PDB for backup and restore jobs, be aware that the following operations are not available:

•
Connecting to a Recovery Catalog. Because the PDB cannot connect to a Recovery Catalog, Quest recommends that you run backups that target the CDB instead of a PDB.
•
Backing up, restoring, and deleting archive logs. If necessary, RMAN automatically restores archive logs during media recovery.
•
Using the CONFIGURE command
•
Using DBPITR and Flashback recovery when using shared undo mode
•
Using Tablespace Point-in-Time Recovery (TSPITR)
•
Using table recovery
•
Using duplicate database
•
Using the IMPORT CATALOG command
•
Using the REGISTER DATABASE command
•
Using report/delete obsolete
•
Using the RESET DATABASE command

Backing up data

You can use the WebUI or CLI to back up the CDB and PDBs.

•
Backing up the CDB and PDBs from the WebUI
•
Backing up the CDB and PDBs from the CLI
Backing up the CDB and PDBs from the WebUI

To set up the plug-in for backup and restore of a CDB using the WebUI, use the same process outlined in Adding a database.

Performing backups is almost identical to the process described in Performing RMAN backups. You must use sets — Backup Selection Set, Backup Options Set, Schedule Set, Target Set, and Advanced Options Set — to create a backup job. Note the following differences:

•
To include all the datafiles of the CDB root container, the seed container, and all the datafiles of the plugged-in PDBs, select the Database node or the All Tablespaces node of a CDB.
•
To include only individual tablespaces or individual datafiles of a CDB, select the specific tablespaces or datafiles of the root container. Note that this option excludes the tablespaces or datafiles of PDBs from the backup.
•
You cannot add a PDB to the WebUI; PDBs are protected as a part of the CDB to which they are plugged. If applicable, you can use the CLI commands described in Backing up the CDB and PDBs from the CLI to back up only the contents of a PDB.
Backing up the CDB and PDBs from the CLI

When you back up the CDB and PDBs from the CLI, you have the option of backing up everything or backing up only the PDB that is targeted by a specific CDB or a specific PDB.

To back up the CDB and all PDBs
rman catalog rcat/rcat@rcatalog
RMAN> connect target /
connected to target database: SALESDB (DBID=3924627550)
using target database control file instead of recovery catalog
RMAN> run { allocate channel ch1 type sbt;
2> backup database include current controlfile
3> plus archivelog; }

The CLI displays the applicable output regarding the status of the backup.

To back up a PDB that is connected to a CDB as a target
RMAN> run { allocate channel ch1 type sbt;
2> backup pluggable database sales_region300_pdb; }

The CLI displays the applicable output regarding the status of the backup.

To back up a PDB that is connected to a PDB as a target
rman nocatalog
 
RMAN> connect target pdbadmin/pdbadmin@sales_region200_pdb
 
connected to target database: SALESDB:SALES_REGION200_PDB (DBID=3022227374)
using target database control file instead of recovery catalog
RMAN> run { allocate channel ch1 type sbt;
2> backup database; }

The CLI displays the applicable output regarding the status of the backup.

Restoring data

You can use the WebUI or CLI to back up the CDB and PDBs.

•
Restoring the CDB and PDBs from the WebUI
•
Restoring the CDB and PDBs from the CLI
Restoring the CDB and PDBs from the WebUI

If you use the WebUI to create and run a backup of a CDB, including its PDBs, you can restore the whole CDB and individual tablespaces or datafiles using the steps provided in Performing RMAN restores. For a more granular restore, you can use the CLI as described in Restoring the CDB and PDBs from the CLI.

Restoring the CDB and PDBs from the CLI

When you restore the CDB and PDBs from the CLI, you have the option of restoring everything or restoring only the PDB that is targeted by a specific CDB.

To restore the CDB

CDBs are restored in a manner similar to restoring non-CDBs. The following example shows the restore of a tablespace from the CDB.

rman catalog rcat/rcat@rcatalog
RMAN> connect target /
connected to target database: SALESDB (DBID=3924627550, not open)
using target database control file instead of recovery catalog
RMAN> run { allocate channel ch1 type sbt;
2> restore tablespace USERS; }
allocated channel: ch1
channel ch1: SID=22 device type=SBT_TAPE
channel ch1: Quest(R) NetVault(R) Backup Plug-in for Oracle. v.12.2.0.9
Starting restore at 28-NOV-18
channel ch1: starting datafile backup set restore
channel ch1: specifying datafile(s) to restore from backup set
channel ch1: restoring datafile 00007 to Q:\APP\ORACLEUSER\ORADATA\SALESDB\USERS01.DBF
channel ch1: reading from backup piece 0rtjacic_1_1
channel ch1: piece handle=0rtjacic_1_1 tag=TAG20181128T002027
channel ch1: restored backup piece 1
channel ch1: restore complete, elapsed time: 00:00:15
Finished restore at 28-NOV-18
released channel: ch1
RMAN>
To restore a PDB that is connected to a CDB as a target
RMAN> run { allocate channel ch1 type sbt;
2> restore pluggable database sales_region300_pdb;
3> recover pluggable database sales_region300_pdb; }

The CLI displays the applicable output regarding the status of the restore.

sqlplus / as sysdba
SQL> alter pluggable database sales_region300_pdb close;
Pluggable database altered.
SQL> exit
rman catalog rcat/rcat@rcatalog
RMAN> connect target /
 
connected to target database: SALESDB (DBID=3924627550)
using target database control file instead of recovery catalog
RMAN> run { allocate channel ch1 type sbt;
2> set until scn=1860018;
3> restore pluggable database sales_region300_pdb;
4> recover pluggable database sales_region300_pdb auxiliary
destination='C:\oracle_recovery';
5> alter pluggable database sales_region300_pdb open resetlogs; }

The CLI displays the applicable output regarding the status of the restore.

rman nocatalog
RMAN> connect target pdbadmin/pdbadmin@sales_region300_pdb
connected to target database: SALESDB:SALES_REGION300_PDB
(DBID=1471149548, not open)
RMAN> run { allocate channel ch1 type sbt;
2> restore database;
3> recover database; }

The CLI displays the applicable output regarding the status of the restore.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating