HP Archive Backup System for OpenVMS Guide to Operations

System Backup to Tape for Oracle Databases
9.2 Configuring Oracle9i Release 2 (9.2.0.2) with SBT
sys$share:mdms$sbtshr_ma64.exe/share, -
sys$share:decc$shr/share
!!! ADDED THIS LINE
9.1.4 Shutdown the database
Before relinking the database, you should shutdown the database.
9.1.5 Relinking the ORA_RDBMS: executables
9.1.6 Startup the database
Now that you have prepared the files for relinking, you must relink the ORA_RDBMS: executables.
Invoke ORA_ INSTALL:ORACLEINS and select RDBMS for rebuild.
Now that you have relinked the Oracle server, you should startup up the database.
9.1.7 Retesting Oracle's Recovery Manager
Before proceeding, you should retest Oracle's Recovery Manager as you did in Section 9.1.1.
9.2 Configuring Oracle9i Release 2 (9.2.0.2) with SBT
This section describes steps for setting up Oracle9i Release 2 (9.2.0.2) with SBT. Oracle9i
Release 2 (9.2.0.2) has support for shared libraries in RMAN. Hence unlike prior versions of
Oracle there is no need for linking the SBT shareable image with Oracle server.
ABS kit provides a special SBT shareable (SYS$SHARE:MDMS$SBTSHR_MA64_9I2.EXE)
for Oracle9i Release 2 (9.2.0.2). This section takes you through steps to be followed to use
MDMS$SBTSHR_MA64_9I2.EXE with Oracle9i Release 2 (9.2.0.2).
9.2.1 Testing Oracle's Recovery Manager before Setting Up System Backup to
Tape
Before doing the configuration for SBT, you should make sure that Oracle's Recovery Manager
is setup and you are able to access it. If you have been using Oracle's Recovery Manager to write
to disk, then you are ready to switch to SBT. If you have not been using Oracle's Recovery Manager,
you should try a backup of a tablespace as shown in Example 9–8
Example 9–8 Oracle's Recovery Manager Backup of System Tablespace to Disk
RMAN> run
2> {
3> allocate channel d1 type disk;
4> backup tablespace system;
5> release channel d1;
6> }
System Backup to Tape for Oracle Databases
Example 9–8 created the file ORA_DB:39EGCJVM_1_1.;1 on my system. Of course your file
name will be different. If everything works then you are ready to link Oracle to SBT. If this step
did not work, then your Oracle Recovery Manager is not setup correctly. You need to correct this
before proceeding.
9.2.2 Authorizing Privileges and Granting Rights to the Oracle Server Account
Before using SBT, you must authorize the VOLPRO privilege and grant the
MDMS_APPLICATION identifier to the Oracle server database administrator account. The
VOLPRO privilege allows the Oracle server to mount volumes that belong to ABS. All volumes
belong to ABS. The MDMS_APPLICATION allows the Oracle server to use the objects in the
MDMS database.
9-6 System Backup to Tape for Oracle Databases