HP A.06.11 - Manual (Page 48)

If you need to export some variables before starting SQL*Plus, listener, or RMAN,
these variables must be defined in the Environment section of the Data Protector
Oracle global configuration file or using the Data Protector GUI.
Configuring multiple Oracle databases simultaneously
In large environments with multiple Oracle databases, it can be time-consuming to
configure each database separately, especially if the configuration parameters need
to be updated frequently.
For these reasons, Data Protector enables you to keep configuration parameters of
multiple databases in a single file. In this way, you can do all necessary updates in
one place. Once the file is ready, you run the Data Protector omniintconfig.pl
command, which reads the file and configures all the Oracle databases specified.
It means that, for each Oracle database, a separate Data Protector configuration file
is created or updated (if it already exists), similarly as if the standard configuration
method were used. If specified, Data Protector also performs a configuration check.
In your configuration file, you specify the following parameters for each Oracle
database:
Table 4 Oracle database configuration parameters
Description Parameter
Manager of managers
MoM
(optional)
Data Protector Cell Manager
Default: Cell Manager of the local client
CellManager
Client with the Oracle Server installed.
In cluster environments, specify the virtual server or, in RAC,
one of the cluster nodes.
Default: local client
Client
Oracle database instance (mandatory) Instance
Integrating Oracle and Data Protector 48