HP (Hewlett-Packard) B6960-96008 Garage Door Opener User Manual


 
Integrating Oracle and Data Protector
Configuring the Integration
Chapter 124
4. Oracle 8i/9i
If you use CLI commands for Oracle integration agents, execute
OMNI$ROOT:[LOG]LOGIN.COM.
5. Oracle 8i/9i
Verify that the -key Oracle8 entry is present in
OMNI$ROOT:[CONFIG.CLIENT]ONMI_INFO, for example:
-key oracle8 -desc "Oracle Integration" -nlsset 159 -nlsId
12172 -flags 0x7 -ntpath "" -uxpath "" -version A.06.00
If the entry is not present, copy it from
OMNI$ROOT:[CONFIG.CLIENT]OMNI_FORMAT. Otherwise, the Oracle
integration will not be shown as installed on the OpenVMS client.
TIP To determine the status of processes (OMNI$I*) and subprocesses
(OMNI$ADMIN_*) on your OpenVMS system, use the following command
procedure:
$@OMNI$ROOT:[BIN}OMNI$DIAGNOSE.COM
This command procedure displays the active parent processes, the
session of job name, and the logfile name.
Configuring Oracle Databases
Configuring an Oracle database involves preparing the environment for
starting a backup. The environment parameters such as the Oracle home
directory and the connection string to the database are saved in the Data
Protector Oracle configuration files on the Cell Manager. The database
must be open during the configuration procedure. The configuration
must be done for each Oracle database.
If a recovery catalog has been created and the Oracle target database has
not yet been registered in the recovery catalog database, this will occur
during the configuration procedure.
To configure an Oracle database, use the Data Protector GUI or CLI.