サポートと今すぐチャット
サポートとのチャット

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

Oracle PDBs: an overview

With Oracle Multitenant Architecture, you can create an Oracle database that functions as a multitenant Container Database (CDB). You also can create non-CDB databases. In a CDB, you can create one or more Pluggable Databases (PDBs) or you can opt not to create any. A PDB is a portable collection of Oracle schemas, schema objects, and nonschema objects that are presented to an Oracle client as a non-CDB database. Prior to Oracle Database 12c, all Oracle databases were non-CDBs. For more information, see the Oracle 12c Multitenant Architecture documentation.

Enabling connection to a PDB

To connect to a PDB that you have created, you must ensure that an entry is added in the Oracle “tnsnames.ora” file and the status of the PDB is in read-write mode. When a PDB is created, a default Oracle service with the same name as the Pluggable Database name is created automatically. However, an entry to the “tnsnames.ora” file might not have been added.

The following is an example of a “tnsnames.ora” file with only an entry of a CDB called salesdb:

SALESDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = salesdb)
)
)
LISTENER_SALESDB =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
)
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
)
)
To enable connection to a PDB
1
After you create a PDB, ensure that the entry for the PDB has been added to the “tnsnames.ora” file.
If not, add the entry manually. The following example shows a manually edited “tnsnames.ora” file after two PDBs, sales_region200_pdb and sales_region300_pdb, have been created:
SALESDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = salesdb)
)
)
LISTENER_SALESDB =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
SALES_REGION200_PDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sales_region200_pdb)
)
)
SALES_REGION300_PDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sales_region300_pdb)
)
)
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
)
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
)
)
2
Ensure that the status of the PDB is set to read-write.
In the following example, a query is run to list the open-mode status of the PDBs. After that, a query is entered to change the open mode of PDB sales_region200_pdb to read-write.
SQLPLUS / AS SYSDBA
SQL> column name format a20
SQL> select name, open_mode from v$pdbs;
NAME OPEN_MODE
-------------------- ----------
PDB$SEED READ ONLY
SALES_REGION200_PDB MOUNTED
SALES_REGION300_PDB MOUNTED
SQL> alter pluggable database sales_region200_pdb open;
Pluggable database altered.
The following example shows how to open all the PDBs with a single query:
SQL> alter pluggable database all open;
Pluggable database altered.
SQL> column name format a20
SQL> select name, open_mode from v$pdbs;
NAME OPEN_MODE
-------------------- ----------
PDB$SEED READ ONLY
SALES_REGION200_PDB READ WRITE
SALES_REGION300_PDB READ WRITE

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
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択