Eric,
     Thanks you very much the delete object command is exactly what I'm
looking for i'll use it in this script once I tweak it a little more to
strip out headers and spaces:
SELECT 'delete object 0', BACKUPS.OBJECT_ID FROM BACKUPS BACKUPS
WHERE (BACKUPS.NODE_NAME='EQPSP01_RMAN') AND (BACKUPS.BACKUP_DATE>{ts 
'2000-11-12 00:00:00'})




"Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>@VM.MARIST.EDU> on
12/12/2001 04:36:53 AM

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

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:  Re: Deleting RMAN versions


Hi James!
No, you need to have 2.2 when you want to use the tdposync utility.
There is another way to get rid of them, but it requires a lot of manual
work and its uses non supported TSM commands.
Issue the following command through the admin commandline interface:
select * from backups where node_name='NODENAME' > c:\Mydir\Myfile.txt
Replace the NODENAME by your clients node name. In caps!!!
This commands lists all files stored on the TSM server for NODENAME.
Have your Oracle Admin compare this list of files with thee catalog entries
and have them return the list of orphaned entries.
Each file is listed with the OBJECT_ID parameter. You can manually delete
entries by using the following command:
delete object 0 OBJECT_ID <= replace this by the object id number.
Remember! This is a unsupported way of deleting backups and you do this on
your own risk!!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines