RE: RMAN Tape Media Volume Identification

  • From: "Mercadante, Thomas F \(LABOR\)" <Thomas.Mercadante@xxxxxxxxxxxxxxxxx>
  • To: <jim.silverman@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 2 May 2007 16:00:41 -0400


I don't think you will find the specific tape volume information in the
Rman repository.  This is managed by the Media Management software.

But I've had luck spinning better reports using the Rc_Database,
Rc_Backup_Set and Rc_Backup_Piece views.

I agree that Rman reporting is quite lame.  But luckily, they have
developed a few views to help us along.

Good Luck,


This transmission may contain confidential, proprietary, or privileged 
information which is intended solely for use by the individual or entity to 
whom it is addressed.  If you are not the intended recipient, you are hereby 
notified that any disclosure, dissemination, copying or distribution of this 
transmission or its attachments is strictly prohibited.  In addition, 
unauthorized access to this transmission may violate federal or State law, 
including the Electronic Communications Privacy Act of 1985.  If you have 
received this transmission in error, please notify the sender immediately by 
return e-mail and delete the transmission and its attachments.

-----Original Message-----

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
Sent: Wednesday, May 02, 2007 3:29 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RMAN Tape Media Volume Identification


We have need to obtain information from RMAN including the specific tape
volumes on which various backupsets are written.  For example, "show me
the information in the catalog for backupsets written between date 1 and
date 2, including the tape volumes".  I've diddled around with the
myriad forms of the RMAN "list" command to try and obtain this
information, but the only success I've had is using the syntax that
includes "primaryKey" (i.e., BS Key) specifiers; without this keyword,
the "Media:" field in the output is empty.

Unfortunately, in order to obtain these keys, you first have to issue
the "list" command that generates scads of output, parse this output for
the BS keys, and then assemble this information into another script that
includes these keys in "list" commands in another RMAN session.

This can't be this hard.

Hopefully I'm missing something perfectly obvious.  Any clues?  TIA...
Jim Silverman
Senior Systems Database Administrator
Solucient, LLC - A Thomson Company
Telephone:   734-669-7641
FAX:            734-930-7611
E-Mail:         jim.silverman@xxxxxxxxxxx


Other related posts: