TSM Support told me , that it is not recommended to abort an audit, since it could happen during repairs, that something is dropped and rebuild from a temporary table. If you stop the audit by killing the process, the result could be quite uggly.
Regards Stefan Holzwarth I'm not sure, if this has its validity for fix=no option > -----Urspr�ngliche Nachricht----- > Von: Daniel Sparrman [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 4. M�rz 2002 16:34 > An: [EMAIL PROTECTED] > Betreff: Re: AW: DB reorg & Audit > > > Hi John > > No, it didn't run with the detail=yes. > > However, if you know what kind of error there is in you DB, > you can run the > audit with sub commands, such as audit db diskstorage fix=yes. > > Yes, you can abort an audit. However, as always, I recommend > having a DB > backup on tape before beginning the audit. > > Best Regards > > Daniel Sparrman > ----------------------------------- > Daniel Sparrman > Exist i Stockholm AB > Bergk�llav�gen 31D > 192 79 SOLLENTUNA > V�xel: 08 - 754 98 00 > Mobil: 070 - 399 27 51 > > > > > "Luscombe John > > (HS)" To: > [EMAIL PROTECTED] > <John.Luscombe@CON cc: > > CORDIA.CH> Subject: > AW: DB reorg & Audit > Sent by: "ADSM: > > Dist Stor Manager" > > <[EMAIL PROTECTED] > > EDU> > > > > > > 2002-03-04 16:15 > > Please respond to > > "ADSM: Dist Stor > > Manager" > > > > > > > > > > Daniel, > > Thanks for the prompt response. I'm pretty sure we do in fact > have errors > in > the DB, hence my suspicion of a required Audit. > > Our machine has 2 Power3 375MHz processors with 1GB memory, I > don't think > the disks are mirrored. > > I assume your Audit was with the Fix=yes option, but did you have > Detail=yes, as this would seem to cause even more checking. > > If we did an unload, then reload and started an audit, but > for whatever > reason it ran too long, could we cancel the audit, then do the reload > again, > after redefining the DB and Logs? If this (or other method) > is feasible > then > it might just allay any fears of starting an audit without > knowing exactly > how long it's going to take. > > Thanks for your help. > > John. > > -----Urspr�ngliche Nachricht----- > Von: Daniel Sparrman [mailto:[EMAIL PROTECTED]] > Gesendet am: Montag, 4. M�rz 2002 15:36 > An: [EMAIL PROTECTED] > Betreff: Re: DB reorg & Audit > > Hi > > You don't have to do a audit to do a unload/load. However, if > you have any > errors in your DB, an audit will be required. > > And unload should take about 6-8 hours, depending on the HW > you're running. > The load should take about equal time. So, count with about > 12-16 hours. > > What kind of RS/6000 are you running? We did a audit of a > 22GB database > which was 87% full. The machine was a dual PowerPC machine > with 1GB memory > and mirrored disks. The audit took about 9 hours. > > Best Regards > > Daniel Sparrman > ----------------------------------- > Daniel Sparrman > Exist i Stockholm AB > Bergk�llav�gen 31D > 192 79 SOLLENTUNA > V�xel: 08 - 754 98 00 > Mobil: 070 - 399 27 51 > > > > > "Luscombe John > > (HS)" To: > [EMAIL PROTECTED] > > <John.Luscombe@CON cc: > > CORDIA.CH> Subject: DB > reorg & Audit > > Sent by: "ADSM: > > Dist Stor Manager" > > <[EMAIL PROTECTED] > > EDU> > > > > > > 2002-03-04 15:04 > > Please respond to > > "ADSM: Dist Stor > > Manager" > > > > > > > > > > Hi TSM folks, > > We are running TSM V4 R2 L1.9 on an RS6K with AIX 4.2.1.9, > the DB is 17,900 > MB and is about 76% full. The machine is a 2 processor WinterHawk (I > think). > > I'm new to TSM, but I'm wondering if someone can give me an > estimate on how > long a DB reorg would run for. > > The follow on question to this is that the documentation > implies an Audit > of > the DB would also be required. Does anyone have experience > that this is > definite? Also, how long would an Audit take? My colleague > who is the lead > for TSM says that IBM have not been able to give any > indication, and we've > heard figures ranging from hours to weeks. > > TIA > > John. > >
