23
57 0 Incr 32918890 2007-10-05 +DG_DB/rac/datafile/tbs_pool_032.dbf
59 0 Incr 32918890 2007-10-05 +DG_DB/rac/datafile/tbs_pool_022.dbf
61 0 Incr 32918890 2007-10-05 +DG_DB/rac/datafile/tbs_pool_021.dbf
63 0 Incr 32918890 2007-10-05 +DG_DB/rac/datafile/tbs_pool_027.dbf
65 0 Incr 32918890 2007-10-05 +DG_DB/rac/datafile/tbs_pool_017.dbf
67 0 Incr 32918890 2007-10-05 +DG_DB/rac/datafile/tbs_pool_026.dbf
69 0 Incr 32918890 2007-10-05 +DG_DB/rac/datafile/tbs_pool_025.dbf
71 0 Incr 32918890 2007-10-05 +DG_DB/rac/datafile/tbs_pool_028.dbf
73 0 Incr 32918890 2007-10-05 +DG_DB/rac/datafile/tbs_pool_019.dbf
The Media ID matches the Medium ID used by Data Protector on every Tape.
Figure 18. Media Information
If we query the rc_backup_piece view on the recovery catalog (ita017) we obtain the same
information:
SQL> select BS_KEY,DEVICE_TYPE,HANDLE,MEDIA from rc_backup_piece where BS_KEY='9266';
BS_KEY DEVICE_TYPE HANDLE MEDIA
---------------------------------------------------------------------------------
9266 SBT_TAPE RAC_POOL_man_ch_1_2<RAC_460:635189150:1>.dbf
10394b75:47060053:1093:0001[[HFP419] HFP419]
Oracle RMAN Restore script
While it is possible to edit the RMAN backup script from within the Data Protector GUI, this is not
possible for the RMAN restore script.
A new enhancement has been implemented in Data Protector to enable this functionality. A new
OMNIRC variable called OB2RMANSAVE needs to be set on the Oracle Server.