Chat now with support
Chat mit 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

Recovering Whole Database to Primary Database Server

This type of recovery is performed when the current Control File and SPFILE are intact but all the datafiles are damaged on the Primary Database Server, and the backup from the Standby Database Server is used for the recovery. You can perform a Complete Recovery or recover the database to a specific point.

An overview of the process to recover the whole database from a backup of the Standby to the Primary Database Server follows.

1
On the Create Restore Job — Choose Saveset page, find the latest available backup on the Standby Database Server that included all the tablespaces, and click Next.
2
On the Create Selection Set page, select the Whole Database node, and click Edit Plugin Options.
3
Click the Restore Options tab, and then select the following:
•
In the Pre-Restore Options section, select Whole Database Restore.
•
In the Restore Options section, select Restore/Recover from User Defined Backup Tag, and specify the User Defined Backup Tag for the Standby Database Server.
4
To perform recovery on the database, that is, reconstruct the database up to the current or specified point, select one of the following options in the Recovery Type section on the Perform Recovery tab:
•
Perform Complete Recovery: Recovers the database to the current time, that is, to the last committed transaction available in the archived and online redo logs.
•
Perform Database Point in Time Recovery: Recovers the database to a specific point-in- time, whether it is a specific time, log sequence number, or SCN.
5
On the Recovery Catalog tab, select the Use Catalog option, and specify the Recovery Catalog connection details.
6
If the Oracle SID of the Primary Database Server is different from the Oracle SID in the standby database, select the Destination Details tab, and complete all fields.
Enter the Target Service of the Primary Database Server, the Oracle SYSDBA User Name, and the Oracle SYSDBA Password.
 
* 
IMPORTANT: In a Data Guard environment, the primary database and standby database have the same database name and the same DBID. However, the Oracle SID might not be the same to differentiate the database servers.
7
In the Target Client list, select the NetVault Backup Client Name of the Primary Database Server.
8
Continue with the restore procedure, including completion of the Schedule and Advanced Options lists.
For more information, see Finalizing and submitting the job.
RMAN automatically chooses the best available Full, Incremental, or Archived Log backups and restores and recovers the database.

Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs)

•
Oracle PDBs: an overview
•
Enabling connection to a PDB
•
Querying CDB, PDB, and non-CDB databases
•
Restrictions for backing up and restoring a PDB
•
Backing up data
•
Restoring data

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
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen