Hello, I'm running 18 Oracle systems on HP-UX which are backed up by TDP for Oracle. The TDP for Oracle version is 5.2.1.0, the TSM servers 5.2.4.1 on AIX 5.2 ML05. Oracle serves are at level 9i and 10g. Our Oracle administrators have written a RMAN script that deletes obsolete backups. I was monitoring the first deletes from RMAN and seen that the delete from RMAN inactivates the TDPO objects on the TSM server. The next expire inventory process will delete the TDPO objects from the TSM database and managed storage. I think this is the reason for BACKDEL=yes, Versions Data Deleted = 0 and Retain Only Version = 0.
In general this works fine in our installation. But in the meantime there is one Oracle system where we have found 'old' TDPO objects in TSM storage but no entries in the RMAN recovery catalog. Even a 'TDPOSYNC SYNCDB' did not remove or inactivate the TDPO objects which should be there anymore. I will test some other things and come back to the list if there's a solution. best regards, Rainer > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Jurjen Oskam > Sent: Friday, October 14, 2005 9:13 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] expiration Oracle backups > > On Thu, Oct 13, 2005 at 07:38:18AM -0700, Neil Rasmussen wrote: > > > When deleting Rman objects on the TSM Server, TDP Oracle uses the > delete > > function on objects....the objects do not move to inactive they are > just > > simply deleted from the TSM Server. > > While the manual says to create nodes for RMAN with Delete Backup > permission set to yes, the manual also says to use a managementclass > that > has Versions Data Deleted = 0 and Retain Only Version = 0. If what you > say > is true (and I have no reason to doubt that :) ), then these settings > are > not relevant, since there are no inactive RMAN objects. Am I right? > > -- > Jurjen Oskam
