HP Archive Backup System for OpenVMS Guide to Operations

System Backup to Tape for Oracle Databases
9.12 Support for Oracle RDB database
9.12.3 Logicals to be specified for use with SBT
The two VMS logicals are to be defined for use with SBT. These logicals need to be defined
before the RMU backup or restore command is executed and should not be specified with the list
of logicals specified with the /LIBRARIAN qualifier.
$DEFINE/PROCESS RMU$LIBRARIAN_PATH librarian_shareable_image.exe
$DEFINE/SYSTEM/EXEC RMU$LIBRARIAN_PATH librarian_shareable_image.exe
This logical must be defined and should point to the SBT shareable image to be loaded and
called by RMU backup and restore operations. For a parallel RMU backup
RMU$LIBRARIAN_PATH should be defined as a system logical so that the multiple processes
created by a parallel backup can all translate the logical.
The default catalog and archive used are ORACLE_DB and ORACLE_DB_ARCHIVE.
The list of process logical names, which SBT may use to specify particular catalogs or archives
for storing or retrieving backup files are MDMS$SBT_ARCHIVE, MDMS$SBT_CATALOG
$DEFINE MDMS$SBT_ARCHIVE REG_RMAN_ARCH
$DEFINE MDMS$SBT_CATALOG REG_ORACLE_DB
9.12.4 SBT Restrctions for Oracle RDB Database
The following scenarios will cause backup not to complete:
• Setting the Drives List in the archive to a number of drives less than the number of data
streams that RMU starts.
• Setting the Maximum Saves in the Archive to a number less than the number of data
streams that RMU starts.
• Specifying more number of writer threads than you have tape drives.
• With OpenVMS Alpha or I64 Operating System, V7.3, SBT backup, using user defined catalog
(defined using logical MDMS$SBT_CATALOG) fails with "invalid archive type".
9-30 System Backup to Tape for Oracle Databases