NetVault Plug-in for Oracle 13.0

Same version of Oracle database software: The version and edition of Oracle for the destination database must be identical to the version and edition of Oracle being used for the source database. This requirement includes identical patch levels.

•

Duplicate Database backup available: A Duplicate Database backup must be completed successfully and made available.

•

Source database in open state: The source database must remain in an OPEN READ WRITE state during the entire Duplicate Database restore process.

•

Auxiliary instance prepared: RMAN’s backup-based Duplicate Database process requires the preparation of an auxiliary instance:

Oracle password file for auxiliary instance created: Required if you want to use a password file versus OS authentication for the auxiliary connection when duplicating to the same host as the source database. For more information on creating a password file, see Creating and Maintaining a Password File in the Oracle Database Administrator’s Guide.

Oracle Net connectivity established to auxiliary instance: The auxiliary instance must be available through Oracle Net by adding the instance to the “tnsnames.ora” file of both the source server and the alternate server. Additionally, on Windows platforms, perform the following command to start the instance:

oradim -new -sid <sid_name>

Auxiliary instance destination directories exist: The following destination directories for the auxiliary instance must be created on the server where the destination database resides. If the destination database stores its datafiles in ASM, the ASM instance name for the destination database must exist.

•

•

•

•

•

PFILE created for auxiliary instance: A client-side PFILE for the Auxiliary Database must be created from the SPFILE of the source database.

•

Start SQL*Plus, and connect with administrator privileges to the source database.

sqlplus sys/<password>@<source_connect_identifier> AS SYSDBA

•

Create a PFILE from the SPFILE.

create pfile = '<PFILE_destination_directory>/

init<auxiliary_sid>.ora' from spfile;

PFILE updated with auxiliary values: The PFILE created for the auxiliary instance must be updated with the parameter values specific to the auxiliary instance.

•

Remove all entries that begin with: <source_sid>.__

•

Update the *.db_name= entry to reflect the name of the destination database.

•

Update the following entries to reflect the destination directory for the auxiliary instance. This directory must exist; however, if the source database stores the datafiles in ASM, the ASM instance name for the destination database should be specified for each of the following control_files and db_create_file_dest parameters:

*.audit_file_dest=

*.background_dump_dest=

*.control_files=

*.user_dump_dest=

*.db_create_file_dest=

*.db_recovery_file_dest=

•

Comment out the following entry by inserting a “#” (number sign) at the beginning of the following entry:

*.dispatchers='(PROTOCOL=TCP) (SERVICE=<source_sid>XDB)'

•

Add the following line to specify the pairs of strings for converting the names of datafiles and tempfiles.

*.db_file_name_convert='<source_db_create_file_dest>/

<source_sid>', '<destination_db_create_file_dest>/

<destination_sid>'

For example:

*.db_file_name_convert=' C:\oracle\oradata\prod',

'c:\oracle\oradata\test'

•

Add the following line to specify the pairs of strings for naming online redo log files:

*.log_file_name_convert='<source_db_create_file_dest>/

<source_sid>', '<destination_db_create_file_dest>/

<destination_sid>'

For example:

*.log_file_name_convert=' C:\oracle\oradata\prod',

'c:\oracle\oradata\test'

Auxiliary instance started in NOMOUNT state: The auxiliary instance must be started in NOMOUNT state with the PFILE that has been updated with the parameter values specific to the auxiliary instance.

•

Start SQL*Plus, and connect with administrator privileges to the auxiliary instance.

sqlplus sys/<password>@<auxiliary_connect_identifier> AS SYSDBA

•

Start the instance in NOMOUNT state.

startup nomount pfile = '<PFILE_destination_directory>/

init<auxiliary_sid>.ora'

Auxiliary instance created from SPFILE from the PFILE.

create spfile from pfile='<PFILE_destination_directory>/

init<auxiliary_sid>.ora';

Exit SQL*Plus.

You must exit SQL*Plus for the Duplicate Database restore to complete successfully.

•

NetVault software and the Plug‑in for Oracle installed: The same version of NetVault software and the plug-in must be installed and configured on the alternate server where the destination database resides.

When configuring the plug-in on the alternate server, ensure that the following Default Attributes are defined:

•

NetVault: Specify the name of the NetVault Server where the source database server was added as a NetVault Client.

•

Do Restore From NetVault Server: Specify the name of the NetVault Server where the source database server was added as a NetVault Client.

•

Restore Backup taken from NetVault Client: Specify the NetVault Machine Name for the source database server.

For more information, see Configuring default settings.

•

Source Database Added to Plug‑in for Oracle Installed on Alternate Server: The source database must be added to the plug-in that is installed on the alternate (standby) server where the destination database resides.

For example, the production Oracle Server is named salesdb. On the alternate server that has the plug-in installed, add a database named salesdb. Complete this step even though the existing database has not yet been cloned to the alternate server. This step forces the plug-in to create a placeholder that can then be accessed during the cloning process when the Oracle database is restored to the alternate (standby) server.

For more information on adding a database, see Adding a database. These instructions work for the original database, as well as the placeholder that you create on the alternate server.

Restoring the Duplicate Database

On the Create Restore Job — Choose Saveset page, find the applicable Duplicate Database backup, and click Next.

On the Create Selection Set page, navigate to the source NetVault Client and database, select the Whole Database node, and click

Click the Clone Database tab, and select the Duplicate Database option.

In the Destination Database section:

•

Specify the Oracle Net Service name of the auxiliary instance in the Target Service field.

•

Specify the Oracle Home for the auxiliary instance.

•

Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the auxiliary instance.

•

Specify the Oracle SYSDBA Password.

•

Select the Use nofilenamecheck option.

In the Duplicate From Database section:

•

Specify the Oracle SID for the source database.

•

Specify the Oracle Home for the source database.

•

Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the source database.

•

Specify the Oracle SYSDBA Password.

In the Target Client list, select the NetVault Machine Name of the alternate server where the destination database resides.

Continue with the restore procedure, including completion of the Schedule and Advanced Options lists.

For more information, see Finalizing and submitting the job.

Performing table-level recovery

Table-level recovery (RECOVER TABLE) is an Oracle-based feature that is available starting with Oracle Database 12.1 Enterprise Edition. If you are using the applicable version of Oracle, you can use the plug-in to recover specific Oracle tables to a specific point.

Oracle Server recovers the tablespaces that contain the tables listed for recovery into an auxiliary instance. Oracle Server then uses data pump to export the table data from the auxiliary instance to the target instance.


	IMPORTANT: The examples shown throughout the following topics are based on using the fully automated version of the auxiliary instance. By using the automated method, the auxiliary instance is fully created and managed by the Oracle Server whenever a destination, that is, a directory in the file system, is provided.

To restore tablespaces to the auxiliary instance, you must provide backups of the system tablespaces, the tablespaces that contain the tables to recover, and the controlfile as it existed at the time of the backup.

The plug-in lets you take advantage of the automated recovery method using an auxiliary instance. For information regarding other methods of performing table-level recovery, see your Oracle documentation. These other methods let you use the RMAN command prompt to recover from backups created by the plug-in.

The following topics provide information for performing a table-level recovery:

•

Uses of table-level recovery

•

Table-level requirements and limitations

•

Configuring channels for table-level recovery

•

Performing table-level recovery from the RMAN CLI

•

Performing table-level recovery from the NetVault WebUI

Uses of table-level recovery

Table-level recovery lets you recover one or more tables or table partitions to a specific point without affecting other tables or database objects. You can use backups created using the plug-in's RMAN backup method to accomplish this process. In addition to other recovery methods, table-level recovery is useful when you need to recover:

•

A few tables to a specific point.

•

Tables that were dropped and purged.

•

Tables that are logically corrupted.

•

A table for which the FLASHBACK TABLE command is unavailable; for example, the Flashback Table cannot rewind because of structural changes, or the target point is older than the undo point.

Table-level requirements and limitations

There are Oracle database-specific limitations and requirements for performing this type of recovery. To perform recovery successfully, review the following requirements and limitations. For more information, including a complete list of constraints, see the table-level recovery information in your Oracle documentation.

•

Table-level recovery is available in the Enterprise Edition of Oracle Server 12.1 or later.

•

To use automated table-level recovery, the directory specified in the “Auxiliary Destination” clause must exist before running recovery. You can use an existing empty directory, or create a directory, if the directory exists before starting the process.

•

You must use the CONFIGURE command to configure the channels in RMAN. The auxiliary database uses the same channels as the target database.

•

Full backups of the tablespaces SYSTEM, SYSAUX, undo, that is, UNDOTBS1, and SYSEXT, if the SYSEXT tablespace is present, must exist. The tablespace that contains the table that is the target of the recovery must also exist.

•

You cannot use table-level recovery to recover: tables that belong to SYS, tables from the SYSTEM and SYSAUX tablespaces, or tables on standby databases.

•

You cannot use the “REMAP” clause to recover tables with named NOT NULL constraints.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

NetVault Plug-in for Oracle 13.0 - User Guide

Restoring a Duplicate Database to an alternate server with an alternate directory structure

Performing table-level recovery

Uses of table-level recovery

Table-level requirements and limitations