Eric,

You should be able to remove the backups through Oracle backup if the backups
exist in your Oracle backup catalog. File should always be removed through
Oracle to ensure that the catalog and the TSM server are in sync. You may need
to query the RMAN ( I am assuming RMAN) catalog to determine which files you
want to remove and delete them through RMAN. I could provide a little more
assistance to exact procedures if you can let me know what versions of the
involved products you are using. I hope this helps a little.

Regards,


Neil G. Rasmussen
TDP Oracle
Phone:  408-256-8265, t/l 276-8265
E-mail:  nrasmuss AT tivoli DOT com


"Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL> on 07/07/2000 07:36:13 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Neil Rasmussen/Tivoli Systems)
Subject:  Re: Management Class for Oracle backups




Thanks to all who replied!
I have updated the VEREXIST and RETEXTRA to 0, just in case this copy group
is misused for non-Oracle backups.
Thanks to you all I learned that the Connect Agent for Oracle creates
backups instead of archives. Due to this I discovered that old backups were
NOT deleted by the Connect Agent! This was because I allowed nodes to delete
archive data and not to delete backup data!
I now have to find a way for the Oracle guys to remove the old backups from
TSM. Since I cannot remove individual backups through admin interfaces, they
have to find a way to do this through the BA client.
Kindest regards,
Eric van Loon