Backing Up Oracle - Computing at Cornell

From the RMAN prompt, we need to allocate a channel before deleting the
backup piece (this is described in the Oracle product documentation in
greater detail).
RMAN> allocate channel for delete type 'sbt_tape';
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: delete_02
RMAN-08500: channel delete_02: sid=15 devtype=SBT_TAPE
RMAN-08526: channel delete_02: MMS Version 2.1.10.0
Next, we change the backup piece to be deleted. The name of the backup
piece is obtained from the list backup; command:
RMAN> change backuppiece '0ecl33t7_1_1' delete;
RMAN-03022: compiling command: change
RMAN-03023: executing command: DELETE
RMAN-08073: deleted backup piece
RMAN-08517: backup piece handle=0ecl33t7_1_1 recid=9 stamp=424775594
At this point, the backup piece 0ecl33t7_1_1 has been deleted from RMAN.
Since we were running in NOCATALOG mode, the information about this
backup in the control file has been deleted. On the TSM server, the backup
data object corresponding to this RMAN backup piece has been marked
inactive. It will be deleted during the next expiration processing on the TSM
server. The select command that was used to view this backup data object
can be used to see that the STATE has change from ACTIVE_VERSION to
INACTIVE_VERSION.
NODE_NAME: JAMAICA_ORACLE
FILESPACE_NAME: \adsmorc
STATE: INACTIVE_VERSION
TYPE: FILE
HL_NAME: \orcnt\
LL_NAME: 0ecl33t7_1_1
OBJECT_ID: 44937
BACKUP_DATE: 2001-03-19 09:15:00.000000
DEACTIVATE_DATE:
OWNER:
CLASS_NAME: DEFAULT
140 Backing Up Oracle using Tivoli Storage Management