I can confirm is it NOT fixed at 6.1.3.2 for Windows. I'm on 6.1.3.3 now, but haven't had the guts to change it back, either....
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Xav Paice Sent: Thursday, May 13, 2010 9:18 PM To: [email protected] Subject: Re: [ADSM-L] TSM 6.1 automatic database backups ----- "Wanda Prather" <[email protected]> wrote: > > John, > Make sure you have in the dsmserv.opt file: > ALLOWREORGTABLE NO > > There is a bug in 6.1 that lets the automatic DB table reorgs go nuts > with the log. Yup - nasty effects. http://www-01.ibm.com/support/docview.wss?uid=swg1IC62978 According to IBM this is fixed in 6.1.3 but I've not had the guts to change back and see if it's OK now - can anyone confirm that this is indeed resolved? > > > 1) On one instance, each day a full TSM DB backup gets done, but > within > about 16-18 hours, the archive filesystem is filling up. The archive > filesystem is 50GB, which is of course much bigger than it was under > 5.5. We have only migrated a fraction of the TSM clients over to > this instance, so I shudder to think how much archive space is going > to > be require when all the TSM clients are in place. Can anybody give > me > any tips on reducing the amount of log data that gets created so it > doesn't fill up so fast? Which would point to IC62978 not being fixed yet. If you try the ALLOWREORGTABLE NO and it fixes the issue, I'd advise raising a PMR (see above)
