As I remember in db2util ver 7 to 8 db2 when db2util passes a delete its like oracle in that its gone ... You may still see the occupancy if expiration and aud lic hasn't run since they passed a delete...
Charles -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Mochnaczewski Sent: Friday, January 02, 2009 2:43 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Question on DB2 expiration When they invioke db2adutl, they see no backups in TSM for the databases they expired , or more apporpriately deleted. Rich -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu]on Behalf Of Richard Sims Sent: Friday, January 02, 2009 3:12 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Question on DB2 expiration On Jan 2, 2009, at 2:13 PM, Richard Mochnaczewski wrote: > Hi *, > > Our DBA group recently expired several terabytes of data. When they > check with their db2util utility, they see no backups. When I run a > select statement on the "virtual" filesystem type API:DB2/AIX64 for > the respective databases I see 100% usage ( some range from 2Tb to > 10Tb but they have all been cleaned up ). The deletion of the backups > have been done on Wednesday and expiration runs daily at 8:00 AM to > completion but the filespaces still show as being at 100%. Is this a > bug ? Running TSM 5.4.30 on AIX 5.3 . But what are the retention policies according to the Copy Group within the Management Class that was used for the backups? What do they see when they invoke the more appropriate utility, db2adutl? (Keep in mind that DB2 utilizes both Backup and Archive.) The DB2 TSM redbook gives a good overview of the whole arrangement. Richard Sims This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
