HP A.06.11 - Manual (Page 36)

Linking Oracle Server with the Data Protector MML
To use the Data Protector Oracle integration, the Oracle Server software needs to
be linked with the Data Protector Oracle integration Media Management Library
(MML) on every client on which an Oracle instance is running.
You do not need to link Oracle Server with the Data Protector MML manually. When
you start backups or restores using the Data Protector GUI or CLI, Data Protector
automatically links Oracle Server with the correct platform–specific Data Protector
MML. However, for testing purposes, you can override this automatic selection. You
can manually specify which platform–specific Data Protector MML should be used
by setting the Data Protector SBT_LIBRARY parameter. On how to set the parameter,
see the util_cmd man page. The parameter is saved in the Data Protector Oracle
instance configuration file.
MML is invoked by the Oracle server when it needs to write to or read from devices
using Data Protector.
Linking on HP OpenVMS systems
On Oracle Server systems running on HP OpenVMS, link the MML
SYS$SHARE:LIBOBK2SHR64.EXE
with the Oracle Server:
1. Make sure Oracle RMAN is set up and you are able to access it. This can be
achieved by performing a test backup using the following RMAN script:
{
allocate channel d1 type disk;
backup tablespace system;
release channel d1;
}
You can skip this step if you are already using RMAN for backing up Oracle.
2. Check the presence of the MML LIBOBK2SHR64.EXE in the SYS$SHARE:
directory.
NOTE:
The logical definition for SYS$SHARE:LIBOBK2SHR64.EXE is
$DEFINE/SYSTEM DP_SBT SYS$SHARE:LIBOBK2SHR64.EXE
.
Integrating Oracle and Data Protector 36