Filter
Top Products
Integrating Oracle and Data Protector
Configuring the Integration
Chapter 1 23
$PIPE@DKC0:[ORACLE9i]ORAUSER.COM > NLA0:
• ORATAB
Depending on the current location of ORATAB, modify
$DEFINE/NOLOG/JOB ORATAB_LOC DKA0:[ORACLE]ORATAB
accordingly. For example, if ORATAB is located in
DKC0:[ORACLE9i], the changes will be:
$DEFINE/NOLOG/JOB ORATAB_LOC DKCF0:[ORACLE9i]ORATAB
Oracle 8i
Execute the OMNI$ROOT:[BIN]DP_ORA8I_RENAME.COM command. This
will update the required Oracle8i executables.
2. Oracle 8i/9i
Uncomment the following lines in OMNI$ROOT:[LOG]LOGIN.COM:
$DEFINE /NOLOG /SYSTEM DP_SBT SYS$SHARE:LIBOBK2SHR32.EXE
$@OMNI$ROOT:[BIN]OMNI$CLI_SETUP.COM
$@OMNI$ROOT:[BIN.PERL]PERL_SETUP.COM
$DEFINE /process PERL_ENV_TABLES "LNM$PROCESS",
"LNM$JOB", "LNM$SERVER", "LNM$GROUP", "LNM$SYSTEM"
3. Oracle 8i/9i
If you run the Media Agent and Data Protector Oracle integration
agents on the same OpenVMS system, modify the group ID of the
omniadmin user as DBA using the MCR AUTHORIZE utility:
a. Log in as a privileged user.
b. Execute:
$set def sys$system
$mcr authorize
UAF>show onmiadmin
UAF>show oracle
c. Compare the accounts for Oracle and omniadmin users. If the
accounts are different, execute:
UAF>modify omniadmin/UIC=UID show
d. Verify the changes of the group ID.