Some of the issue depends on how the DBA did the "fix". If they started 
expiring the backups, TSM would automatically catch the expiration notices and 
handle them.
 
However, if the DBA just disconnected and then reconnected the catalog to get 
of the backups, you will have to manually delete the backed-up data.
 
I've had a couple of customers whose DBAs didn't want to wait for expirations 
("it's take too long!"), and I've seen terabytes of data orphaned.
 
Imagine my thrill...
 
--
Mark Stapleton (mark.stapleton AT berbee DOT com)

________________________________

From: ADSM: Dist Stor Manager on behalf of Shawn Geil
Sent: Tue 8/7/2007 12:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Oracle rman and tdp out of sync



I have found that my DBA was not deleting backups from TSM via RMAN when
removing the backup from the control file.  I now have that issue
corrected.  I am having some challenges getting the orphaned backups out
of TSM however.

Environment:
Oracle 9.2 on AIX 5.2
TSM 5.2 on AIX 5.1
TDP 5.2
no catalog using the control file

We have tried doing an RMAN crosscheck but it only finds the backups in
the control file not the ones only in TSM.  We do have delete obsolete
now working correctly to handle the backup in both the control file and TSM.

I have been reading about tdposync but that only looks to work if you
are using the RMAN catalog.  Is this correct and if so does anyone know
of another method to clear these up.  I have seen the delete object
information but would prefer not to use an unsupported undocumented command.

S
--
************************************************************************
Shawn Geil, Senior Systems Administrator         shawn.geil AT washburn DOT edu
Information Systems and Services          phone number 785.670.1010.2305
Washburn University                                 Topeka, Kansas 66621
************************************************************************