Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerProtect Data Manager 19.16 Oracle RMAN User Guide

Configuration file requirements for connection to local databases

As required for certain ddbmcon program operations, you must complete the required configuration settings to enable the authentication method that you want the program to use. Each authentication method has its own requirements for parameter settings in the configuration file.

During the Oracle RMAN agent installation, the configuration file template rman_agent.cfg is installed in the $RMAN_AGENT_HOME/config directory. To enable a particular authentication method, you must set the required parameters in the rman_agent.cfg configuration file.

The configuration file template includes the following information.

# #############################################################################
#
# rman_agent.cfg
#
# All rights reserved.
#
# Oracle RMAN agent 19.16
#
# This template is designed to help users to configure the authentication of
# RMAN agent. Check the product administration guide for a complete list of
# all the supported parameters and rules for editing the configuration file.
#
# Make a copy of this file before making any modifications.
# To enable a parameter, uncomment or add the parameter in the file and
# specify its value.
#
# #############################################################################
#
# #############################################################################
# Oracle parameters.
# There can be repetitive sections of Oracle parameters. The Oracle database
# to which the parameters belong is described in the section name: SID_name.
# The name here must be replaced by the SID of the database.
# :
# #############################################################################
[SID_name]
# ORACLE_SERVICE =
# ORACLE_USER =
# ORACLE_OS_USER =
# TNS_ADMIN =
# RMAN_CATALOG_SERVICE =
# RMAN_CATALOG_USER =
# RAC_BACKUP_NODE_IP =
# DELETE_ARCHIVE_LOGS =
# FILESPERSET =
# MAXOPENFILES =
# SECTION_SIZE =
# BLOCK_SIZE =
# RAC_NODE_IP_1 =
# RAC_NODE_FQDN_1 =
# RAC_NODE_IP_2 =
# RAC_NODE_FQDN_2 =
# RAC_NODE_IP_<n> =
# RAC_NODE_FQDN_<n> =
# ENABLE_BROWNFIELD_DISCOVERY =
# CROSSCHECK = {TRUE|FALSE}
# PRIMARY_DBNAME = <Data Guard primary database name>
# :
[GENERAL]
# EXCLUDE_SID = <Oracle SIDs>
# ALLOW_BACKUP = <Oracle SIDs>
# IGNORE_ORATAB_INACTIVE_SID = {TRUE|FALSE}
# GATHER_STATS = {TRUE|FALSE}

To set a particular parameter in the configuration file, remove the number sign (#) at the start of the parameter line and add the parameter value after the equal sign (=).

You can complete the following settings in the configuration file:

  • SID_name is mandatory for each authentication method when you set any parameters in the file for a particular system ID (SID). [SID_name] (for example, [SID_orcl]) must appear on a separate line before all the parameter settings for the SID.

    For any supported Oracle version in a stand-alone or RAC system, SID_name must match the SID that runs on the local host.

    NOTE:Each Oracle SID on the same system requires its own entries in the configuration file. You must use the same configuration file for all the Oracle SIDs.
  • ORACLE_SERVICE is mandatory for database authentication and Oracle wallet authentication. This parameter specifies the TNS or Net service name of the Oracle database.
  • ORACLE_USER is mandatory for database authentication only. This parameter specifies the database username as saved in the lockbox.
  • ORACLE_OS_USER is mandatory for operating system authentication when the username for connection is different than the ORACLE_OSDBA_USER username. This parameter specifies the operating system user that connects to the Oracle database for operating system authentication. When this parameter is set, ORACLE_OSDBA_USER is ignored.
  • TNS_ADMIN is mandatory for database authentication and Oracle wallet authentication when the Oracle Net configuration files including tnsnames.ora reside in a non-default directory. This parameter specifies the pathname of the non-default directory. When this parameter is not set, the system default directory $ORACLE_HOME/network is used.
  • RMAN_CATALOG_SERVICE is mandatory when an RMAN catalog is used for backup or recovery of the database. This parameter specifies the TNS name of the RMAN catalog.
  • RMAN_CATALOG_USER is mandatory for each authentication method when an RMAN catalog is used. This parameter specifies the catalog database username as saved in the lockbox.
  • RAC_BACKUP_NODE_IP is highly recommended in an Oracle RAC environment only. In the Oracle RAC environment, select a single node to be the backup node and set this parameter to the hostname or IP address of the backup node.

    In the Oracle RAC environment, the backup operations are performed on the node that is specified in the RAC_BACKUP_NODE_IP parameter setting. A backup operation fails when the specified node is unavailable.

    NOTE:

    The backup node setting in the PowerProtect Data Manager UI takes precedence over the RAC_BACKUP_NODE_IP parameter setting in the configuration file for the same asset. Assign a preferred node in Oracle RAC environment provides details about the backup node setting in the PowerProtect Data Manager UI.

    The backup node setting is not applicable for self-service or stand-alone backups.

  • DELETE_ARCHIVE_LOGS is optional. This parameter specifies whether to delete the archive logs after performing a centralized log backup. When this parameter is set to TRUE, the archive logs are deleted after the log backup.
  • FILESPERSET is optional. This parameter specifies the maximum number of files that RMAN can include in a backup set. The value must be an integer from 1 to 64, inclusive.

    NOTE:

    As an alternative to setting the parameters FILESPERSET, MAXOPENFILES, SECTION_SIZE, and BLOCK_SIZE in the configuration file, you can set the options Files Per Set, Maximum Open Files, Section Size, and Block Size, respectively, in the protection policy configuration in the PowerProtect Data Manager UI. Protection policies for Oracle database protection provides details about the protection policy options.

    The configuration file parameter settings take precedence over the option settings in the PowerProtect Data Manager UI. These parameter and option settings apply only to centralized backups. The FILESPERSET and SECTION_SIZE settings apply only to full, incremental cumulative, and incremental differential backups—not to log backups. SECTION_SIZE does not apply to multistream backups.

  • MAXOPENFILES is optional. This parameter specifies the maximum number of input files that a backup or copy can have open at a given time. The value must be an integer greater than 0.
  • SECTION_SIZE is optional. This parameter specifies the size in KB, MB, or GB of each backup section in a multisection backup. In the backup set, each backup piece contains the blocks from one file section. The specified value must be <n>K or <n>M or <n>G, where <n> is an integer greater than 0. K means kilobytes, M means megabytes, and G means gigabytes.

    If you specify a section size that is larger than the size of the file, then RMAN does not use a multisection backup for the file. If you specify a small section size that would produce more than 256 sections, then RMAN increases the section size to a value that results in exactly 256 sections.

    NOTE:SECTION_SIZE does not apply to multistream backups.
  • BLOCK_SIZE is optional. This parameter specifies the number of KB of data that the Oracle database reads for the backup operation. The value must be a multiple of the minimum physical block size of the Oracle database. The value must be <n>K, where <n> is an integer between 1 and 1024 inclusive. K means kilobytes.
  • RAC_NODE_IP_1, RAC_NODE_FQDN_1, RAC_NODE_IP_2, RAC_NODE_FQDN_2, RAC_NODE_IP_<n>, RAC_NODE_FQDN_<n> are optional. These parameters specify the IP addresses and fully qualified domain names (FQDNs) of the RAC nodes. These RAC node settings are required only if the asset discoveries are not working on the RAC system and the asset report refers to the system as "Stand-alone" instead of "RAC".
  • ENABLE_BROWNFIELD_DISCOVERY is optional. This parameter specifies whether to discover the database copies that were backed up before being managed by PowerProtect Data Manager. When this parameter is set to TRUE, PowerProtect Data Manager discovers the copies that the Oracle RMAN agent backed up before the asset was managed by PowerProtect Data Manager.
  • CROSSCHECK is optional. This parameter specifies whether to perform a crosscheck operation before recovering the database. When this parameter is set to TRUE, the crosscheck operation is performed before the database recovery.
  • PRIMARY_DBNAME is mandatory for a Data Guard logical standby database. This parameter specifies the case-sensitive primary database name, which is the name from the output of the SQL query command select name from v$database; that is run on the primary database.
  • EXCLUDE_SID is optional. This parameter specifies the list of Oracle SIDs to exclude from PowerProtect Data Manager discovery.
  • ALLOW_BACKUP is optional. This parameter specifies the comma-separated list of Oracle SIDs to allow stand-alone Oracle backups. This parameter is only applicable for stand-alone backups.
  • IGNORE_ORATAB_INACTIVE_SID is optional. This parameter specifies whether to ignore any "database not available" errors for inactive Oracle system identifiers (SIDs) in the /etc/oratab file during the application system discovery. The default value is FALSE. When this parameter is set to FALSE or not set, the ddbmcon process reports the errors for any unavailable databases that are listed in the /etc/oratab file to PowerProtect Data Manager during the application system discovery. When the parameter is set to TRUE, the ddbmcon process does not report the errors to PowerProtect Data Manager during the discovery.
  • GATHER_STATS is optional. This parameter specifies whether to run the temp segment SQL query and report the results to PowerProtect Data Manager. To fix the error ORA-01652: unable to extend temp segment, set this parameter to TRUE.

The following topics provide more details about the configuration requirements of each particular authentication method.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\