Backing Up Oracle - Computing at Cornell

B.5.3 Renaming / deleting the TSM filespace
Support normally recommends that you rename the existing filespace and
then wait a few weeks until backups have accumulated again. After some
period of time, you can delete the old (renamed) filespace in order to delete
the backups that you no longer want to keep.
The filespace for a specific node can be renamed from the TSM Server using
a TSM administrative client session (dsmadmc).
To see the existing filespaces for a specific node:
Query filespace
To rename the filespace:
Rename filespace
To delete the filespace:
Delete filespace
Both the rename and delete of a filespace is on a per-Node basis. Therefore,
if your Oracle backups are using different TSM nodenames for each instance,
then you can work with these on an individual basis.
Note: The Oracle 8i RMAN has a SYNCH capability to look at the backups in
the RMAN catalog and compare them with the Tape library vendor software
(in this case, the TSM server). In version 2.2 of the TDP for Oracle, this
functionality is being provided to remove the unwanted backup objects. See
Appendix C, “TDP for Oracle Version 2.2” on page 209.
208 Backing Up Oracle using Tivoli Storage Management