Aborting Sessions; Oracle Rman Metadata And Data Protector Media Management Database Synchronization - HP Data Protector A.06.11 Integration Manual

For details, see the omnib and omnir man pages or the HP Data Protector command
line interface reference.
Example
To resume the backup session 2009/05/13–1, run:
omnib –resume 2009/05/13–1

Aborting sessions

You can abort currently running sessions by clicking the abort button.
If, during a session, RMAN or SQL*Plus do not respond when requested, Data
Protector automatically aborts the session. By default, Data Protector waits for the
response for 5 minutes. Using omnirc or environmental variables
OB2_RMAN_COMMAND_TIMEOUT and OB2_SQLP_SCRIPT_TIMEOUT, you can
modify this time interval.
For details on how to set environmental variables, see
variables" on page 55. For details on how to set the corresponding omnirc options,
see the online Help index: "omnirc option". Note that environmental variables override
omnirc options.
Oracle RMAN metadata and Data Protector Media
Management Database synchronization
This section describes how to synchronize the Oracle RMAN metadata with the Data
Protector Media Management Database.
The RMAN metadata contains information about the target database. RMAN uses
this information for all backup, restore and maintenance operations. The metadata
can be stored either in the recovery catalog database or in the control files.
Data Protector is the media manager that Oracle needs to perform tape storage
backups and restores.
Data Protector has its own data protection policy that is not automatically synchronized
with Oracle RMAN metadata. To have both catalogs synchronized, run the following
command using RMAN:
allocate channel for maintenance type 'sbt_tape' parms
'SBT_LIBRARY=Path_to_Data_Protector_MML,
ENV=(OB2MAINTENANCE=1)';
138 Integrating Oracle and Data Protector
"Setting environmental