HP Archive Backup System for OpenVMS Guide to Operations

System Backup to Tape for Oracle Databases
9.9 System Backup to Tape Defaults
exit
$ exit
Note
Since the RMAN script is just a DCL command procedure, the /AFTER_SCHEDULE
qualifier cannot be used to link schedules that execute RMAN scripts. That is, schedules
that execute RMAN scripts cannot be assigned to the /AFTER_SCHEDULE qualifier
on any schedule object. This is a current design limitation. Please refer to release
notes section 5.3.6 for more details on this restriction.
Note
When specifying a format in the backup command you must put in a % character that
creates unique names being sent to SBT.
You can put Oracle's Recovery Manager command line in the scheduler command and execute a
stored script through a cmdfile.
9.9 System Backup to Tape Defaults
9.9.1 Archive Name
9.9.2 Catalog Name
9.9.3 I/O Block Size
The SBT feature of ABS/MDMS has defaults. This section describes these defaults.
If you do not pass the parms="ENV=(MDMS$SBT_ ARCHIVE=archive_name)" in an Oracle
Recovery Manager allocate command, SBT will use the default ORACLE_DB_ ARCHIVE
archive.
If you do not pass the parms="ENV=(MDMS$SBT_ CATALOG=catalog_name)" in an Oracle
Recovery Manager allocate command, SBT will use the default ABS$CATA-
LOG:ORACLE_DB catalog.
If you do not pass the parms="ENV=(MDMS$SBT_IO_BLOCK_ SIZE=block_size)" in an
Oracle Recovery Manager allocate command, SBT will use a block size of 65024 bytes when
writing blocks on the I/O device. This has nothing to do with the block size that Oracle sends
down to be written on the I/O device.
9.9.4 MDMS$SBT_RESTORE_SINGLE_CHANNEL=TRUE
If you do not pass params="ENV=(MDMS$SBT_RESTORE_SINGLE_CHANNEL=TRUE)"
in an Oracle Recovery manager allocate command,SBT will not treat this restore as a single
channel restore and will force a dismount operation after restoring each backup piece.
9.9.5 System Backup to Tape Logicals Names
describes the logical names used to control your SBT sessions. These logical names can be a
system wide logical (DEFINE/SYSTEM) or be defined in your Oracle Recovery Manager
scripts. When using in Oracle's Recovery Manager scripts, the logical is declared when you allocate
a channel with the keyword of ENVfor the keyword parms. The following example shows
how the MDMS$SBT_ARCHIVE and MDMS$SBT_IO_BLOCK_SIZE logicals are defined as
a process logical with Oracle's Recovery Manager allocate command:
run
{
allocate channel t1 for 'sbt_tape'
parms="ENV=(MDMS$SBT_ARCHIVE=OFFSITE_ARCHIVE,
9-18 System Backup to Tape for Oracle Databases