Advanced Configuration - Oracle iDataAgent

In the CommCell Console each instance references an Oracle database. Hence it is necessary to discover the instances which can then be used to backup data. You can discover or add an instance as described in the following sections:

Enabling Automatic Instance Discovery

When automatic instance discovery is enabled, the existing Oracle database instances are discovered as follows:

Every 168 hours.
Whenever the Communications Service (GxCVD) is restarted (such as after a computer reboot).

This capability ensures that all instances are accounted for on a regular basis for backups.

Automatic instance discovery will not detect the manually created databases in an instance. Make sure that there is an entry in /etc/oratab for manually created oracle instance which contains manually created databases. Then, this instance is automatically discovered when you enable instance discovery.

Use the following steps to enable automatic instance discovery:

From the CommCell Browser, navigate to Client Computers |<Client>.
Right-click Oracle, and then click Properties.
Select the Enable Instance Discovery check box.
Click OK.

Setting the Automatic Discovery Frequency

When instance discovery is enabled, Oracle instances are automatically discovered every 168 hours or whenever the Communications Service (GxCVD) is restarted. Use the following steps to modify the default discovery time interval.

From the CommCell Browser, navigate to Client Computers.
Right-click the <Client>, and then click Properties.
Click the Registry Key Settings tab.
Click Add.
In the Name box, type nORACLEINSTANCEDISCOVERYINTERVAL
In the Location box, select or type OracleAgent.
In the Type box:
- On Windows client
Select REG_DWORD.
- On Unix client
Select Value.
In the Value box, type the time interval to discover instances.
For example, to discover instances every two hours, type 2.
Click OK.

Manually Discovering Instances

If you have manually created an Oracle database, then you must manually discover the corresponding instance. Automatic instance discovery will not detect the manually created databases.

In addition, you can also use the manual discovery process to discover the Oracle databases at any point in time. Use the following steps to manually discover instances:

From the CommCell Browser, navigate to Client Computers | <Client>.
Right-click Oracle, point to All Tasks, and then click Discover Instance.
Click Yes to confirm discovery of instances.

Manually Adding an Instance

During automatic instance discovery, options such as oracle home path and user account, connect string are preset. When instances are manually added, these options can be customized. Use the following steps to manually add an instance:

From the CommCell Browser, navigate to *Client Computers \|< Client* >. Right-click Oracle, point to All Tasks, and then click New Instance (ORACLE SID**).
In the Instance (ORACLE SID) box, type the Instance name. In the User Account box, type the login credentials to access the Oracle client. In the ORACLE HOME box, type the Oracle application install path. In the Storage Policy used for the data of default subclient box, select a storage policy name.
Click the Details tab. In the Connect String box, type the credentials to access the Oracle database. For example, sys/pwd12@orcl4. Click the Storage Device tab. In the Storage Policy used for user command backup of data box, select a storage policy. In the Storage Policy used for all Archive Log backups box, select a storage policy name. Click OK.

Creating an On Demand Instance

You need to create an On Demand instance to perform on demand backup operations. When creating an On demand instance, a default subclient is automatically created for the instance. The content for the default subclient will be specified in the RMAN script that is run through the Command Line Interface.

Once an On Demand Instance is created, it cannot be changed into a traditional instance.

Use the following steps to create an On Demand instance:

From the CommCell Browser, navigate to Client Computers | <Client>.
Right-click Oracle, point to All Tasks, and then click New On Demand Instance.
Click Yes to confirm the creation of an On Demand Instance.

Configuring the Oracle Home Directory

Oracle HOME directory refers to the location where the Oracle application resides. When instances are discovered, the home path is automatically assigned to the instance. However, you can modify the home path location for an instance at any point of time. Use the following steps to configure the Oracle HOME directory:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle|.
Right-click the <Instance>, and then click Properties.
In the ORACLE HOME box, type the path to Oracle Home directory. Alternatively, you can use Browse to locate the path.
Click OK.

Configuring the TNS ADMIN Directory

When an instance is configured, by default, the TNS_Admin directory is created in the Oracle HOME\network\admin path. Use the following steps to change the path for the TNS_ADMIN directory:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle|.
Right-click the <Instance>, and then click Properties.
Click the Details tab.
In the TNS_ADMIN folder box, type the location for the TNS Admin directory. Alternatively, you can use Browse to locate the path.
Click OK.

Managing Container databases (cdb)

In the CommCell Console each Oracle 12c container database (CDB) maps to an instance. Once you have added an instance for the container database, you can create subclients and backup sets as you would for any Oracle database instance.

Adding a container database

From the CommCell Browser, navigate to *Client Computers \|< Client* >. Right-click Oracle, point to All Tasks, and then click New Instance (ORACLE SID**).
In the Instance (ORACLE SID) box, type the container database name. In the User Account box, type the login credentials to access the Oracle container database. In the ORACLE HOME box, type the Oracle container database application install path. In the Storage Policy used for the data of default subclient box, select a storage policy name.
Click the Details tab. In the Connect String box, type the credentials to access the Oracle container database. For example, sys/pwd12@orcl4. Click the Storage Device tab. In the Storage Policy used for user command backup of data box, select a storage policy. In the Storage Policy used for all Archive Log backups box, select a storage policy name. Click OK.

Configuring User Accounts for Backups

In order to perform backup and restore operations, you need to create and configure the following user accounts on the Oracle client:

User Account with administrative privileges to access the Oracle application.
On Unix clients, the user should be part of the user group assigned during the iDataAgent install. You can also use the operating system user account to verify the rights to perform all backup and restore operations for the associated Oracle instance.

On Windows clients, the user should be part of local administrator group and also part of the ora_dba group with read/write permissions on Calypso folder. You can use the Impersonate user account to verify the rights to perform all backup and restore operations for the associated Oracle instance.
User account to access the Oracle database. You can use separate accounts to access the standard database and the Recovery Catalog database. The account information is provided as a connect string with the following information:
- Database user ID.
- Password for the user ID.
- Oracle Service name.
The user account for standard database should have the following privileges:
- Administration privileges (default) or Oracle database administration privileges.
- SYSDBA and ALTER SYSTEM system privileges.
Alternatively, instead of using administrator user account with SELECT ANY TABLE privilege, you can also create user accounts with lesser privileges for accessing specific objects:

For example:
- SELECT ON "SYS"."V_$DATABASE"
- SELECT ON "SYS"."V_$DATAFILE"
- SELECT ON "SYS"."DBA_TABLESPACES"
- GRANT SELECT ON "SYS"."V_$ARCHIVE_DEST" TO "USER_NAME
The Recovery Catalog database user account must have recovery catalog owner privileges.

Additional accounts (except Impersonate User) should be established by Oracle database administrator.

Configuring User Account to Access the Oracle Application

Use the following steps to configure the user account to access the Oracle application:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>, and then click Properties.

On Windows client:
- Click Change.
- In the User Account box, type the user account name.
- In the Enter Password box, type the password for the user account.
- In the Confirm Password box, retype the password, and then click OK.

On Unix clients:

In the User Account box, type the user account to access the Oracle application.

Click OK.

Configuring User Account to Access the Oracle Database

Use the following steps to configure the user account privileges to access the Oracle database:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>, and then click Properties.
Click the Details tab.
In the Connect String box, type the connect string to connect to the Oracle database as following:
- Type the Database user ID.
- Click the Password box, in the Enter Password box, type the password for the user ID.
- In the Confirm Password box, retype the password, and then click OK.
- Type the Oracle service name.
For example:

sysdba/<password>@<orcl

where, sysdba is the Database User ID, <password> is the password of the Database User ID, and orcl is the Oracle service name.
Click OK.

Disabling the RMAN Crosscheck

By default, during a data aging operation, an Oracle CROSSCHECK is performed by the system to synchronize the entries in the CommServe database with the RMAN catalog. Use the following steps to disable the cross check operation:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle .
Right-click the <Instance>, and then click Properties.
Click the Details tab.
Select the Disable RMAN cross check check box.
Click OK to close the warning message.
Click OK.

Managing Subclients

When you create an instance, a default subclient is automatically created. The default subclient includes the entire database associated with that instance, which includes all components, such as the log files and control files. However, you can create user-defined subclients to backup the specific components or conditions, such as the following:

Whether a backup will be offline or online.
Whether the entire database will be backed up, or only a subset of objects within the database should be backed up.
Whether the archive logs need to be backed up separately
Manage your archive log and control file backups.

If a new database object is added to the database, and if none of the subclients contain that database object , then that object is automatically assigned to the content of the default subclient.

Creating a Subclient for Offline Backups

During an offline backup, the database is shutdown and is not available for use. Since incremental backups require access to various tablespaces and datafiles, it is always recommended that you perform a full backup of the database when it is offline. The full backup includes all the datafiles, tablespaces, and control file of the Oracle database. Note that, offline backups do not include the archived log files.

Offline backups can be performed when the database is in offline or online mode. If the database is online, it shuts down the database, performs the backup and then brings up the database back.

In order to backup the Oracle database when it is offline, you need to create a separate user-defined subclient for offline backup. Make sure that the database is in the MOUNT mode during the backup.

A static listener must be configured for offline backups with lights out script when the Oracle database is in open mode. See When do we configure a static listener for additional information.

Use the following steps to create a subclient for offline backups:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Click Offline Database.
Click the Storage Device tab.
In the Data Storage Policy box, select the storage policy name.
Click OK.

Creating a Subclient for Online Backups

In some environments, it may not be possible to bring down the entire database to perform an offline backup. In such situations, you can choose online backups, where the database will be up and running during the backup.

You can perform either a full backup or incremental backup of the Oracle database when it is online. Since full backups includes all the datafiles, tablespaces and logs, it is very time consuming, hence you can plan for a full online backup less frequently (say, on weekly basis). On the other hand, incremental backups includes the data and logs that have been changed after the last full backup, they are faster and can be performed more frequently (say, on a daily basis).

If a new database object is added to the database, and if none of the subclients contain that database object , then that object is assigned to the content of the default subclient

Use the following steps to create a subclient for online backups:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Click Online Database.
Click the Storage Device tab.
In the Data Storage Policy box, select the Storage policy.
Click OK.

Creating a Subclient to Backup Individual Datafiles/Tablespaces

You can also create subclients to backup specific datafiles and tablespaces, which undergo frequent changes in the Oracle database.

Use the following steps to create a subclient to backup individual datafiles and tablespaces:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Click Online Subset.
Select the database objects to be included in the backup.
Click the Storage Device tab.
In the Data Storage Policy box, select the storage policy name.
Click OK.

Creating a Subclient for Selective Online Full Backups

Selective Online Full backup is a full backup performed when an Oracle database is online and is copied to a selective copy (during an auxiliary copy operation) from which it can be restored.
The advantage of this type of backup is that both the data and logs use the same storage policy, which means that they reside together on the same media. They are completely self-contained for restore and long term archiving purposes. This is especially useful in disaster recovery situations by alleviating the need to locate different offsite media from various jobs to gather the necessary data and logs to recover the database. Also, the data aging rules for selective online full backups are different from regular full backups, as both data and logs are aged together under the same storage policy.

When performing the selective online full backup, note the following:

A selective online full backup job will wait for other Oracle backup jobs currently running on the same instance to complete before it begins.
For this type of backup, both data and archive logs will use the same storage policy as defined for data in the subclient, and will ignore the storage policy setting for archive logs (which is defined at the instance level).
During selective online full backups, if the data streams (defined at the subclient level) is less than the archive log streams (defined at the instance level), then both the data phase and the archive log phase will use the same number of streams defined for the data in the subclient, and will ignore the number of streams set for the archive logs.
Selective online full backup jobs are not preemptable nor restartable. Similarly, oracle log backup jobs that are submitted during selective online full backups (data phase) also cannot be preempted nor restarted.
While the data backup phase of a selective online full backup is running, the only other Oracle backup jobs that are allowed to run on the same instance are archive log backups. During the log backup phase of a selective online full backup, no other Oracle backups are allowed to run (neither logs nor data) on the same instance.
If other Oracle archive log backup jobs are running at the same time as the selective online full backup, they will be forced to use the same storage policy used by the selective online full backup during the time-frame in which the selective online full backup job is running, and will be included in the same auxiliary copy operation.
Selective Copy is supported only for Selective Online Full job and offline jobs for Oracle.
Extended Retention Rules are applicable for only Selective Online Full and Offline jobs.

Use the following steps to create a subclient for performing selective online full backups:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Select the Selective Online Full check box.
Click the Storage Device tab.
In the Data Storage Policy box, select the storage policy name.
Click OK.

See Data Aging Rules for Selective Online Full Backups for more data aging rules for selective online full backups.

If you want to create a subclient for selective online full backup on multiple instances or clients instead of navigating to each client and creating the subclients, then, use this qscript.

Use the following steps to create a subclient for selective online full backups from the command line using qscript:

From the command prompt, logon to the CommServe using the qlogin command.

Example: To log on to CommServe leonard64.devemc.com with user name user1:

qlogin -cs leonard64.devemc.com -u user1

Password:

Run the command to create a subclient for Oracle Selective Online Full backup.

D:\>qcreate sub client -cs leonard64.devemc.com -c dbserve4 -a Q_ORACLE -i auto -n "NEWSUB" -sp "ying_data" -f "auto

Run the command to execute the qscript.

D:\>qoperation execscript -sn SetSubClientProperty.sql -si 'c=dbserve4' -si 'a=Q_ORACLE' -si 'i=auto' -si 'b=default' -si 's=NEWSUB' -si 'Oracle Online Selective Full' -si '1' -si '2'

For more information about the parameters and arguments, see qscript.

Enabling Selective Online Incremental Backup

When performing selective online incremental backups, note the following:

Selective online incremental backup jobs can be suspended in the Job controller and restarted from the point of failure like regular backups.
Selective online incremental backups are not copied to Selective copy.
Selective online incremental backup will use the storage policies specified for both data and logs.

You can enable and disable selective online incremental backup using sql scripts.

Enable selective online incremental backup:

qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si JMSOFIncrSupport -si y -si 1

Disable selective online incremental backup:

qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si JMSOFIncrSupport -si n

Creating a Subclient for Log Backups

Archive logs are required to recover database transactions that have been lost due to an operating system or disk failure. You can apply these archive logs to an online backup in order to recover a database.

Though online full backups can include both data and logs, because of their importance in recovering data, it is recommended that you create separate subclients to backup archive log files.

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Clear the Data checkbox.
Select the Backup Archive Log check box.
Click the Storage Device tab.
In the Data Storage Policy box, select the storage policy name.
Click OK.

If you want to create a subclient for Log backups on multiple instances or clients instead of navigating to each client and creating the subclients, then, use this qscript.

Use the following steps to create a subclient for Log backups from the command line using qscript:

1.	From the command prompt, logon to the CommServe using the qlogin command.	Example: To log on to CommServe leonard64.devemc.com with user name user1: qlogin -cs leonard64.devemc.com -u user1 Password:
2.	Run the command to create a subclient.	D:\>qcreate sub client -cs leonard64.devemc.commvault.com -c dbserve4 -a Q_ORACLE -i auto -n "NEWlog" -sp "ying_data" -f "auto"
3.	Run the command to disable Data option.	D:\>qoperation execscript -sn SetSubClientProperty.sql -si 'c=dbserve4' -si 'a=Q_ORACLE' -si 'i=auto' -si 'b=default' -si 's=NEWlog' -si 'Oracle Backup Mode' -si '1' -si '2'
4.	Run the command to disable Backup Control File option.	D:\>qoperation execscript -sn SetSubClientProperty.sql -si 'c=dbserve4' -si 'a=Q_ORACLE' -si 'i=auto' -si 'b=default' -si 's=NEWlog' -si 'Backup Control Files' -si '0' -si '2'
5.	Run the command to disable Delete Archive log option.	D:\>qoperation execscript -sn SetSubClientProperty.sql -si 'c=dbserve4' -si 'a=Q_ORACLE' -si 'i=auto' -si 'b=default' -si 's=NEWlog' -si 'Archive Log Deleting' -si '0' -si '2'

For more information about the parameters and arguments, see qscript.

Configuring Backups for Standby Database

Standby databases can be backed up when they are in offline or online state. If the database is online, the iDataAgent detects the standby database mode by checking the database role and automatically disables the log switch operation.

Use the following steps to configure backups for standby database:

Add an instance for the Standby database. Alternative, you can auto discover the database.
From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Select the backup mode. Choose one of the following;
- Offline Database - if the backup is performed when database is offline.
- Online Database - if the backup needs to be performed on the online database
Click the Storage Device tab.
In the Data Storage Policy box, select the storage policy name.
Click OK.

Configuring Archive Log Destinations

When you backup archive logs, you can specify the locations from where the log backups should be performed. This capability enables you to schedule backup operations from different log destinations on the same subclient. If necessary, you can also delete the logs after the backup. For more information, see Deleting the Logs after a Backup

Setting Up the Log Destination for Deletion

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Log Destinations tab.
Select the Select ArchiveLog Destinations for Backup check box.
Click Add, type or select the Archive log file destination, and then click OK.
Click OK.

Deleting the Logs after a Backup

Ensure that the logs in the specified location are backed up. This may cause data loss if those archive logs are not backed up.

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Log Destinations tab.
Select the Select ArchiveLog Destinations for Delete check box.
Click Yes to close the warning message.
In the Confirmation box, type Confirm.
Click OK.
Click Add.
Type or select the Archive log file destination.
Click OK.
Click OK.

Disabling Log Switch

When performing archive log backups, the current redo log file is closed (even if it is not filled up completely) and the next redo log file is used for writing using a log switch. The closed redo log file is then archived during the log phase. Use the following steps to disable the log switch:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle|<Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab.
Clear the Data checkbox.
Select the Backup Archive Log check box.
Select the Disable Switch Current Log check box.
Click OK.

Enabling Log Deletion after Backup

When backing up archive logs, by default the logs are not deleted after the backup operation. Use the following steps to enable deletion of logs soon after the backup.

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab.
Select the Archive Delete check box.
Click OK.

See Deleting Archive Logs After a Specific Backup for more information.

Managing Control Files

As the Control file stores the status of the physical structure of the database. It is required when you want to recover the database to the current state. Hence it is important to include control files in your backups. By default, control files are included in the subclient for selective online full backups. You can also include/exclude control files for online or offline backups. The following sections describe the methods by which you can backup control files.

Enabling Automatic Backup of Control Files for All Subclients

You can configure the instance to automatically backup Control Files whenever you a backup the subclient in that instance.

Use the following steps to enable automatic backup of control files for all the subclients in the instance.

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>.
Click the Details tab, in the Ctrl File Autobackup box,
- Select Configure ON. This will backup the control file separately.
- Alternatively, select Configure Off to backup the control file along with the datafile.
Click OK.

Enable/Disable Control File Backups for a Specific Subclient

If the control file backup is enabled at the instance level, you can also include/exclude control files for backups from a specific subclient. Use the following steps to enable control file backups for a specific subclient.

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle | <Instance>.
Right-click the <Subclient>,and then click Properties.
Click the Content tab.
Select the Backup Control File check box.
Click OK.

Configuring Table Restores

By default, all data is backed up which includes tablespaces. If you want to restore individual tables, you need to enable table level backup.

Enabling Table Browse for Restores

In order to backup and restore database tables, you need to enable table level backups for the subclient. Use the following steps to enable backups at table level.

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab, and then click the Options tab.
Select the Enable Table Browse check box.
Click OK.

Setting Up the Auxiliary Instance

By default, when you restore database tables to a target instance, the system automatically duplicates the source database to an auxiliary instance in a temporary staging location specified during the restore operation. The database will be automatically imported from this auxiliary instance after the restore.

Use the following steps to set up a specific database as an auxiliary instance. This is useful when you want to restore a table to a specific failure point.

1. Copy the init<SID>.ora file from the source database to the auxiliary database instance.

2. Update the database name and the database file locations in the init<SID>.ora file for the auxiliary database instance.

3. Add the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the init<SID>.ora file. These parameters will redirect the datafiles, temp files, and log files to the auxiliary instance. Windows Clients:
DB_FILE_NAME_CONVERT=('sourcE_of_df_path/','dup_of_df_path/','source_of_temp_path/','dup_of_temp_path/',...)

LOG_FILE_NAME_CONVERT=('source_of_log_path/redo','dup_of_log_path/redo')

Unix Clients:

DB_FILE_NAME_CONVERT=(source_of_df_path/,dup_of_df_path/,source_of_temp_path/,dup_of_temp_path/,...)

LOG_FILE_NAME_CONVERT=(source_of_log_path/redo,dup_of_log_path/redo)

4. Add the log_archive_dest_1 parameter is added to the init<SID>.ora file on the auxiliary instance.

5. Restart the Oracle Services, if using Windows clients.

6. Add the destination instance name in the Listener.ora and Tnsnames.ora files. If using a different host, add the duplicate database instance name in the Listener.ora file on the destination host and Tnsnames.ora files on the destination and source hosts. Also, add the original database name in the Tnsnames.ora file on the destination host. DUPDB = (DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521))

(CONNECT_DATA = (SERVER = DEDICATED)

(SERVICE_NAME = dupdb) (UR=A) ) )

7. Restart the Listener. $lsnrctl reload

8. Ensure that the auxiliary instance is in NOMOUNT mode. sql> startup nomount;

Configuring Lights Out Script for Offline Backups

In order to perform offline backups of the Oracle database, all users must be logged out of the database and it must be completely shut down. When the database is online, you can enable a graceful shutdown of the database using lights out script that will notify the users about the shutdown and set a specific wait time for the users to logout of the database. Use the following steps to configure lights out script for offline backups:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | < Instance>.
Right-click the <Subclient>, and click Properties.
Click the Content tab, and then click Offline Database.
Click the Backup Arguments tab, and then click the Offline Arguments tab.
Select the Lights Out Script check box.
Select the Warning checkbox to display a warning message on the physical node.
In the Delay Time box, select the delay time interval in minutes.
In the Sleep Time (min) box, select or type the number of minutes to wait between retry attempts.
In the Sleep Time (sec) box, select or type the number of seconds that you want the script to wait between retry attempts to shut down the database and check the status.
In the Tries Number box, type the number of times the system must retry to attempt to shut down the database.
Select the Use SQL Connect checkbox to connect to the oracle database.
Click OK.

Including Server Parameter (SP) File during Backups

The Server Parameter file (SPFile) contains the database startup information. By default, the backups do not include the SPFile.

Use the following steps to include SPFile during backups:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab.
Select the Back up SP FILE check box.
Click OK.

Enabling Backups of Flash Recovery Area

Flash Recovery Area is a specific area in the disk storage that exclusively holds a copy of all backup-related components, such as image copies, redo logs, and control file auto backups. This facilitates faster restores of backup data and minimizes restores from tapes during restore operations. Use the following steps to enable backup of flash recovery area:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab.
Select the Protect backup recover area check box.
Click OK.

Using Recovery Catalog for Backups

By default, recovery catalog is not used for backup and restore. As the recovery catalog contains metadata about RMAN operations for each registered database, it is recommended to include recovery catalog in backups. The metadata information is useful when you want to restore and recover the database after a crash. Use the following steps to use the Recovery Catalog for backups:

Verify that you have a recovery catalog database created using the following command:
From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>, and then click Properties.
Click the Details tab.
Select the Use Catalog Connect check box.
In the Catalog Connect string box
- In the User Id box, type the Database user ID.
- Click the Password box, in the Enter Password box, type the password for the user ID.
- In the Confirm Password box, retype the password, and then click OK.
- Type the Oracle service name.
For example:

sysdba/<password>@<orcl

where, sysdba is the Database User ID, <password> is the password of the Database User ID, and orcl is the Oracle service name.
Click OK.

Synchronizing the Control File with the Recovery Catalog

It is a good practice to synchronize the recovery catalog with the control file, as the control file contains the latest backup information, which is need to perform restores.

Use the following steps to synchronize the control file with the recovery catalog:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle | < Instance >.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab, and then click the Options tab.
Select the Resync Catalog check box.
Click OK.

Configuring Streams for Backups

By default, backup data is sent to media in two streams. This means that a database is sent to media during a backup in two parallel waves. This results in backup taking about half the time to complete as it otherwise would if only one stream is used.

You can increase the number of streams used for backups for a particular subclient provided the number of streams does not exceed the maximum number configured in the subclient's storage policy. Increasing the number of streams for a subclient further reduces the amount of time a backup takes to complete. For example, increasing the number of streams from 2 to 3 enhances backup time from one-half that of a single stream to one-third.

Keep in mind that the same number of streams used for performing a backup will be needed to restore the data.

Data Backups

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Storage Device tab.
In the Number of Data Backup Streams box, type or select the number of data backup streams.
Click OK.

Log Backups

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <Instance>, and then click Properties.
Click the Storage Device tab, and then click the Log Backup tab.
In the Number of Archive Log Backup Streams box, type or select the number of log backup streams.
Click OK.

Enhancing Backup Performance

Several options are available for enhancing backup performance and reduce the network bandwidth used for performing backups. These options include:

Specifying the number of datafiles and archive files to be included in each RMAN backupset.The default value is 32.
Specifying the maximum size for each RMAN backupset. By default no limits are defined. By default no limits are defined.
Specifying the number of open datafiles that can be read by RMAN during the backup. The default value is 8.
Specifying the maximum size of data blocks used during backups. The default value is 262144 Kb.

In addition to the above configurations, you can also enable distribution of data across disks during backup operations. See Enhancing Backup Performance for more details

Use the following steps to enhance the backup performance:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | < Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab.
In the Data Files per BFS box, type or select the number of datafiles in each RMAN backup set.
In the MAX Backup Set Size (kb) box, type or select the size of backup set allowed for RMAN backup set.
In the Archive Files per BFS box, type or select the number of archive files in each RMAN backup set.
In the Max Open Files box, type or select the number of datafiles that RMAN can read from simultaneously during a backup operation.

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
Right-click the <instance>, and then click Properties.
Click the Details tab.
In the Block Size box, type or select the size of the block for backup and restore operations.
Click OK.

Assigning Unique Identification Tags for Backups

You can assign unique identification tags for all backup operations from a specific subclient. These tags can be used during a restore operation to easily identify a particular backup. Use the following steps to assign unique identification tag for backups.

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> and click Properties.
Click the Backup Arguments tab.
In the Oracle Tag box, type the tag name.
Click OK.

Excluding Data During Backups

You can configure a subclient to skip the following data during backup operations:

Read-only tablespaces
Offline tablespaces
Inaccessible Datafiles and Archived redo log files

Use the following steps to exclude data during backup operations:

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle| <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab, and then click the Options tab.
Select the SKIP READ ONLY check box to exclude the read only tablespaces.
Select the SKIP OFFLINE check box to exclude the offline tablespaces.
Select the SKIP INACCESSIBLE check box to exclude inaccessible data and log files.
Click OK.

Validating Database for Backups

Prior to running backup operations, you can validate a backup job, which will cause RMAN to simulate the backup for the purpose of determining whether the backup can be successfully restored. Once a validate job is completed, you can view the log files of the job to identify and correct any validation issues.

During validation, the backup jobs are simulated without the media, you can view the log files of the job to identify and correct any validation issues.

Use the following steps to enable validation of backup jobs:

Prior to running a backup, you can check the following:

Datafiles for physical and logical block corruption
Database files exist and are in the correct location.

From the CommCell Browser, navigate to Client Computers | <Client>| Oracle | <Instance>.
Right-click the Subclient and click Properties.
Click the Backup Arguments tab, and then click the Options tab.
Select the Validate check box.
Click OK.

Command Line Operations

You can add, modify, or delete several configurable properties for the Oracle iDataAgent from the command line interface.

Command line configuration enables you to:

configure the same properties across multiple clients simultaneously.
reuse the same configurations for additional entities.

The following sections describe the available command line configurations:

Log on to the Commserve

To run command line operations you must first login to the CommServe as follows:

From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:
qlogin -cs <commserve name> -u <user name>
For example, to log on to CommServe 'server1' with username 'user1':
qlogin -cs server1 -u user1

Configuring Instances

Creating an Instance

From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:
qcreate instance -c client -a iDataAgent -n instance -dsp defaultstoragepolicy -csp cmdlinestoragepolicy -lsp logstoragepolicy -hu Host User (Windows|Unix) [-ntp ntpassword] -oh oracleHome -ocu connectUser -ocp connectPassword -ocs connectService -ct usecatalog [-ctu catalogUser] [-ctp catalogPassword] [-cts catalogService] [-tns tnsadmin]

Example for creating an instance on the Unix client:

[root@client1 Base]# ./qcreate instance -c client1 -a Q_ORACLE -n instance1 -dsp sp1 -csp sp2 -lsp sp3 -hu oracle -oh /oracle/oracle10g ocu sys -ocp sys -ocs dctmdb -ct yes -ctu snap -ctp snap -cts test

Created instance successfully.

[root@client1 Base]#

You can execute a CreateOracleInstance qscript too using qoperation execscript qcommand to create an instance.

Modifying an Instance

From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:
qoperation execscript -sn SetOracleInstanceProperties.sql -si 'clientname' -si 'Q_ORACLE' -si 'instancename' -si �instanceprop� -si �instancevalue� -si �instanceproptype�

Examples:

[root@client1 Base]# ./qmodify instance -c client1 -a Q_ORACLE -i instance1 -csp sp2 -lsp sp3

Modified instance successfully.

[root@client1 Base]#

To modify Oracle Home

qoperation execscript -sn SetOracleInstanceProperties.sql -si 'client1' -si 'Q_ORACLE' -si 'instance1' -si 'Oracle Home' -si '/oracle/oracle10g'
To modify TNS Admin location

qoperation execscript -sn SetOracleInstanceProperties.sql -si 'client1' -si 'Q_ORACLE' -si 'instance1' -si 'TNS admin path' -si '/oracle/oracle10g/network/admin'
To Disable RMAN crosschek

qoperation execscript -sn SetOracleInstanceProperties.sql -si 'client1' -si 'Q_ORACLE' -si 'instance1' -si 'Oracle RMAN Cross Check' -si '1' -si 2
To Configure Controlfile Auto Backup

qoperation execscript -sn SetOracleInstanceProperties.sql -si 'client1' -si 'Q_ORACLE' -si 'instance1' -si �Auto Backup Control File� -si '1' -si 10

to disable Auto backup of control file, use �si �2� for instancevalue(0-for Not Configure, 1- Configure On, 2- Configure OFF)
Modifying Block Size in instance properties (To change Block size value to 1M)

qoperation execscript -sn SetOracleInstanceProperties.sql -si 'client1' -si 'Q_ORACLE' -si 'instance1' -si 'Oracle block size' -si 1048576 -si 10
To change user impersonation/connect sting/Catalog credentials

qopetation execscript -sn setOraclecredentials.sql -si c=clientName|allclients -si t=Catalog|DB|Impersonate| [username] -p2 <password> -si <username>
To change the Connect string user name/ password for all databases of all clients, where the password is in plain text

qoperation execscript -sn SetOracleCredentials.sql -si allclients -si t=DB -p2 passwd -si sys
To change credentials for impersonate user (applicable for windows clients only)

qoperation execscript -sn SetOracleCredentials.sql -si c=client1 -si t=Impersonate -p2 passwd -si domainname\username
To change Catalog user name/password for all the databases under one client

qoperation execscript -sn SetOracleCredentials.sql -si c=client1 -si t=Catalog -p2 passwd -si rman
To Change Log and command line Storage Policies

qmodify instance -c client -a dataagenttype -i instance -csp cmdlinestoragepolicy -lsp logstoragepolicy

Configuring the Subclients

Creating a Subclient

Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameters and attributes:
qcreate subclient -c client -a dataagenttype -i instance -n subclient -sp storagepolicy -f content

Example to create subclient with default options:

[root@client1 Base]# ./qcreate subclient -c client1 -a Q_ORACLE -i instance1 -n subclient1 -sp sp1 -f " "

Created subclient successfully.

Modify Subclient

Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameters and attributes:
qoperation execscript -sn SetSubClientProperty.sql -si 'c=<client name>' -si 'a=<agent type>' -si 'i=<instance name>' -si 'b=<backup set name>' -si 's=<subclient name>' -si <subclient property> -si <subclient property value> -si <subclient property type >

Examples:

Creating Oracle Selective Online Full Subclient

Create the subclient

qcreate subclient -c client1 -a Q_ORACLE -i instance1 -n "SOF" -sp "ora_data" -f " "
Enable Selective Online Full

qoperation execscript -sn SetSubClientProperty.sql -si 'c=client1' -si 'a=Q_ORACLE' -si 'i=instance1' -si 'b=default' -si 's=SOF' -si 'Oracle Online Selective Full' -si '1' -si '2'

Creating Oracle Offline Subclient and enabling the Light Out script

Create the subclient

qcreate subclient -c client1 -a Q_ORACLE -i instance1 -n "OFFLINE" -sp "ora_data" -f " "
Enable the offline option

qoperation execscript -sn SetSubClientProperty.sql -si 'c=client1' -si 'a=Q_ORACLE' -si 'i=instance1' -si 'b=default' -si 's=OFFLINE' -si 'Oracle Backup Mode' -si '2'
Enable the Light Out script

qoperation execscript -sn SetSubClientProperty.sql -si 'client1' -si 'a=Q_ORACLE' -si 'i=instance1' -si 'b=default' -si 's=OFFLINE' -si 'Light out Script� -si �1� -si '2'

Creating Log Only Subclient

Create the subclient

qcreate subclient -c client1 -a Q_ORACLE -i instance1 -n "LOGONLY" -sp "ora_data" -f " "
Disable Data Option

qoperation execscript -sn SetSubClientProperty.sql -si 'c=client1' -si 'a=Q_ORACLE' -si 'i=instance1' -si 'b=default' -si 's=LOGONLY' -si 'Oracle Backup Mode' -si '1'
Disable Delete Archive Log Option

qoperation execscript -sn SetSubClientProperty.sql -si 'c=client1' -si 'a=Q_ORACLE' -si 'i=instance1' -si 'b=default' -si 's=LOGONLY' -si 'Archive Log Deleting' -si '0' -si '2�

Configuring BFS values

Change datafile per BFS to 10:

qoperation execscript -sn SetSubClientProperty.sql -si 'c=client1' -si 'a=Q_ORACLE' -si 'i=instance1' -si 'b=default' -si 's=command_test1' -si �Oracle Data FPS� -si '10' -si '7'
change archive files per BFS to 12:

qoperation execscript -sn SetSubClientProperty.sql -si 'c=client1' -si 'a=Q_ORACLE' -si 'i=instance1' -si 'b=default' -si 's=command_test1' -si �Arch per bfs� -si '12' -si '8'

Configuring number of data streams

Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameters and attributes:

qoperation execscript -sn SetSubClientProperty.sql -si c=<client_name> -si 'a=Q_ORACLE' -si i=<instance_name> -si 'b=default' -si s=<subclient_name> -si 'Oracle Data backup streams' -si '<stream_value>� -si '7'

Example:

Example to set the number of data streams to 4:

qoperation execscript -sn SetSubClientProperty.sql -si c=client1 -si 'a=Q_ORACLE' -si i=orcl -si 'b=default' -si s=FullSc -si 'Oracle Data backup streams' -si '4' -si '7'

Delete Subclient

Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameters and attributes:
qdelete subclient -c client -a dataagenttype -i instance -s subclient

Example:

[root@client1 Base]# ./qdelete subclient -c client1 -a Q_ORACLE -i instance1 -s subclient1

Deleted subclient successfully.

Enabling Multiple Backup Copies

You can take multiple copies of the data or log backups using RMAN command line. During restores, even if one of the copies is missing or corrupted, the restore operation will automatically failover to the other copy and restore the data.

To utilize the PARALLELISM option, you need to set the initial parameter in pfile or spfile.

Example:

BACKUP_TAPE_IO_SLAVES=TRUE

Configure device type.

Example:

RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;

Specify two copies of data.

Example:

RMAN> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 2;

Specify two copies of log backups.

Example:

RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 2;

Add the environmental variables for the client and instance on which the iDataAgent is installed.

Example:

allocate channel ch1 type 'sbt_tape'

PARMS="<software_install_path>/Base/libobk.so,

ENV=(CvClientName=<client_name>,

CvInstanceName=<instance_name>)"

Once you set the parameters, restart the Oracle database and perform backup operations from the CommCell Console.

Example: To restart the database,

Connect to the database.
SQL> connect admin/admin@orcl as sysdba
Shutdown the database.
SQL> shutdown
Mount the database.
SQL> startup mount;
Change to archivelog mode.
SQL> alter database archivelog;
Open the database.
SQL> alter database open;

Modifying an Agent, Instance, or Subclient

There are several configurable properties available for your agent that can be modified from the agent, instance, or subclient level as per need.

It is recommended that that you do not modify the properties of a subclient when a job is in progress for that specific subclient. If a job is in progress, either wait for the job to complete or kill the job from the Job Controller.

The following table describes the properties that can configured from the agent, instance, and subclient levels.

Option	Description	Related Topics
Change Storage Policies	You can modify the storage policies in any of the following situations: To include a different media for the backup operation. To use a storage policy with a different retention criteria. You can change the storage policies from the subclient level. From the CommCell Browser, right-click the subclient. Click Properties. Click Storage Device. Select the Storage policy from the drop-down menu. Click OK.	Refer to Storage Policies.
Rename a Subclient	You can rename a subclient: From the CommCell Browser, right-click the subclient. Click Properties. Type the new name in the Subclient name field. Click OK.
Rename an Instance	You can rename a subclient. From the CommCell Browser, navigate to *Client Computers \| <Client>\| Oracle. Right-click the <Instance>, and then click Properties* In the Instance( Oracle SID) box, type the instance name. Click OK.
Data Transfer Options	You can efficiently configure the available resources for transferring data secured by data protection operations from the subclient level. This includes the following: Enable or disable Data Compression either on the client or the MediaAgent. Configure the transfer of data in the network using the options for Network Bandwidth Throttling and Network Agents. You can configure the data transfer options. From the CommCell Browser,right-click the subclient. Click Properties. Click Storage Device. Click Data Transfer Option tab. Choose the appropriate software compression option for this subclient. Select Throttle Network Bandwidth and set the required bandwidth. Click OK.	Refer to Data Compression and Network Bandwidth Throttling.
View Data Paths	You can view the data paths associated with the primary storage policy copy of the selected storage policy or incremental storage policy. You can also modify the data paths including their priority from the subclient level. From the CommCell browser, right-click the subclient. Click Properties. Click Storage Device. Select Storage Policy from the drop-down menu. Click Data Paths.
Configure a Subclient for Pre/Post Processing of Data Protection	You can add, modify or view Pre/Post processes for the subclient. These are batch files or shell scripts that you can run before or after certain job phases. From the CommCell browser, right-click the subclient. Click Properties. Click Pre/Post Process. Click one of the following phases and type the full path of the process that you want to execute during that phase. Alternatively, click Browse to locate the process (applicable only for paths that do not contain any spaces). PreBackup Process PostBackup Process PreSnap Process PostSnap Process Click OK. Select Run Post Backup Process for all attempts to run a post backup process for all attempts. For subclients on Windows platforms, Run As displays Not Selected. If you want to change the account that has permission to run these commands, click Change. In the User Account dialog box, select Use Local System Account, or select Impersonate User and enter the user name and password. click OK. If you selected Local System Account, click OK to the message advising you that commands using this account have rights to access all data on the client computer.	Refer to Pre/Post Processes.
Configure Activity Control	You can enable backup and restore operations from the agent and subclient level. However, you can enable restore operations only from the agent level. From the CommCell browser, right-click the subclient. Click Properties. Click Activity Control, select or clear option(s) as desired. Click OK.	Refer to Activity Control.
Configure User Security	You can configure user security from the agent or subclient level. You can perform the following functions: Identify the user groups to which this CommCell object is associated. Associate this object with a user group. Disassociate this object from a user group. From the CommCell browser, right-click the subclient. Click Properties. Click Security. Select the appropriate user groups to which you want to associate to the CommCell object from the Available Groups pane, and then move the user group to the Associated Groups pane. Click OK.	Refer to User Administration and Security.
Enable/Disable Data Encryption	You can enable data encryption from the suclient level.Encryption must be enabled at the client level prior to configuring any instances residing on that client. From the CommCell browser, right-click the subclient. Click Properties. Click Encryption. Select the desired encryption. Click OK.	Refer to Data Encryption.
Enable/Disable Encryption for Third-party Command Line Operations	You can enable data encryption for the command line operations from instance properties: From the CommCell Browser, navigate to *Client Computers \| <Client>\| Oracle. Right-click the <Instance>, and then click Properties. Click the Encryption* tab. Select the desired Encryption from the following: None Media Only (MediaAgent Side) Network and Media (Agent Side) Network Only (Agent Encrypts, MediaAgent Decrypt Click OK.
View Software Version and Installed Updates	The Version tab, at the Agent level displays the software version of the component. From the CommCell browser, right-click the agent. Click Properties. Click Version. Click OK.
CommCell Configuration Report	The CommCell Configuration Report provides the properties of the CommServe, MediaAgents, clients, agents, SRM agents, subclients, and storage policies within the CommCell based on the selected filter criteria. From the CommCell browser, click Reports icon. Select CommCell Configuration. Click Run.	Refer to CommCell Configuration.

Deleting an Agent, Instance, or Subclient

The following sections describe the steps involved in deleting an agent, instance, or subclient.

When you delete an instance or backupset, the associated data is logically deleted and you can no longer access the corresponding data from CommCell Console for recovery purposes.

Refer to the troubleshooting article on Recovering Data Associated with Deleted Clients and Storage Policies for information on how to recover data if you accidentally delete an entity.

Deleting an Agent

You need to uninstall or DeConfigure the agent software from the client computer before deleting from CommCell Browser. After you delete the client software, you can either leave the corresponding data intact for appropriate action or you can remove the data immediately. If you choose to remove the data immediately, you must delete the agent from the CommCell Browser. If you delete the agent, all of the agent's data is irretrievably lost.

You cannot delete an agent while operations for that agent are running.

From the CommCell Browser, navigate to Client Computers | <Client>.
Right-click the <Agent>, and then click Delete.
A confirmation message is displayed with the following message:
This operation will permanently delete the data backed up from this level and it cannot be restored.
Click OK to continue with the deletion operation., or click No to abort the deletion.

Deleting an Instance

Consider the following before deleting an instance:

When you delete a specific instance all job schedules and job histories that pertain to any of the levels within the deleted instance are deleted.
You cannot delete an instance if it is being backed up. Attempts to delete an instance under such conditions cause the deletion to fail. If a backup is in progress, either wait for the backup to complete or kill the backup job using the Job Manager. Once the backup is no longer in progress, you can delete the instance level.
You cannot delete an instance if there is only one instance present for an agent. To delete the final instance, you must remove the agent software from the client computer.

From the CommCell Browser, right-click the instance that you want to delete, click All Tasks and then click Delete.
click Yes to confirm the deletion. (clicking No cancels the deletion and retains the node.)
Type the requested phrase in the Enter Confirmation Text dialog box and click OK. This should delete the instance.

Deleting a Subclient

Consider the following before deleting a subclient:

You cannot delete a default subclient.
Schedules associated with the subclient are also automatically deleted.

From the CommCell Browser, navigate to Client Computers | <Client> | <Agent> | <Instance>.
Right-click the <Subclient> that you want to delete, and then click Delete.
A confirmation message is displayed, asking if you want to delete the subclient.
Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion.

1.	Copy the init<SID>.ora file from the source database to the auxiliary database instance.
2.	Update the database name and the database file locations in the init<SID>.ora file for the auxiliary database instance.
3.	Add the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the init<SID>.ora file. These parameters will redirect the datafiles, temp files, and log files to the auxiliary instance.	Windows Clients: DB_FILE_NAME_CONVERT=('sourcE_of_df_path/','dup_of_df_path/','source_of_temp_path/','dup_of_temp_path/',...) LOG_FILE_NAME_CONVERT=('source_of_log_path/redo','dup_of_log_path/redo') Unix Clients: DB_FILE_NAME_CONVERT=(source_of_df_path/,dup_of_df_path/,source_of_temp_path/,dup_of_temp_path/,...) LOG_FILE_NAME_CONVERT=(source_of_log_path/redo,dup_of_log_path/redo)
4.	Add the log_archive_dest_1 parameter is added to the init<SID>.ora file on the auxiliary instance.
5.	Restart the Oracle Services, if using Windows clients.
6.	Add the destination instance name in the Listener.ora and Tnsnames.ora files. If using a different host, add the duplicate database instance name in the Listener.ora file on the destination host and Tnsnames.ora files on the destination and source hosts. Also, add the original database name in the Tnsnames.ora file on the destination host.	DUPDB = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = dupdb) (UR=A) ) )
7.	Restart the Listener.	$lsnrctl reload
8.	Ensure that the auxiliary instance is in NOMOUNT mode.	sql> startup nomount;

Advanced Configuration - Oracle iDataAgent

Table of Contents

Agent

Instance

Subclient

Enabling Selective Online Incremental Backup

Creating an Instance

Modifying an Instance

To modify Oracle Home

To modify TNS Admin location

To Disable RMAN crosschek

To Configure Controlfile Auto Backup

Modifying Block Size in instance properties (To change Block size value to 1M)

To change user impersonation/connect sting/Catalog credentials

To change the Connect string user name/ password for all databases of all clients, where the password is in plain text

To change credentials for impersonate user (applicable for windows clients only)

To change Catalog user name/password for all the databases under one client

To Change Log and command line Storage Policies

Creating a Subclient

Modify Subclient

Creating Oracle Selective Online Full Subclient

Create the subclient

Enable Selective Online Full

Creating Oracle Offline Subclient and enabling the Light Out script

Create the subclient

Enable the offline option

Enable the Light Out script

Creating Log Only Subclient

Create the subclient

Disable Data Option

Disable Delete Archive Log Option

Configuring BFS values

Change datafile per BFS to 10:

change archive files per BFS to 12:

Configuring number of data streams

Delete Subclient