Backing Up Oracle - Computing at Cornell

3. delete expired backup;
RMAN> delete expired backup;
RMAN-03022: compiling command: delete expired
RMAN-03023: executing command: delete expired
RMAN-08073: deleted backup piece
RMAN-08517: backup piece handle=STARTER/426340296/12/1 recid=12 stamp=426340296
RMAN-08073: deleted backup piece
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
The RMAN catalog now matches what is on the TSM server.
B.5.2 TSM object exists without a corresponding RMAN reference
This type of situation is much harder to overcome. You should only undertake
the following procedures if you are completely knowledgeable, since this will
remove valid backups as well as inconsistent backups if not done correctly.
If a situation is encountered where there are RMAN backups that are not
marked inactive on the TSM server, there are two ways to remove these
unwanted active backups.
Use the unsupported API sample program to delete the individual backup
objects.
On the TSM server, rename/delete the filespace (containing all the
backups).
B.5.2.1 Using the API sample program to delete objects
There is a program called Sample that can be used to access the individual
API objects on TSM. The Sample program is not supported, but development
has included it in an uncompiled state as part of the API installation.
Appendix E of the manual Tivoli Storage Manager: Using the Application
Program Interface, SH26-4123, has some references to setting up and
running this application. This manual can be downloaded from the Web site:
http://www.tivoli.com/support/storage_mgt/adsm/pubs/admanual.htm
This Sample application has the capability to work with individual API backup
objects and can delete a specific backup object.
Appendix B. Troubleshooting 207