Re: which Onchecks ?

This is good for me to hear. :-)) Except for the part where I've been wasting time on them for so long. I guess old habits die hard. <snicker> One place where I'll never stop using them is before an upgrade. I've been nailed on that before by the upgrade failing due to some corruption in a systabauth that should have been seen and repaired before the upgrade. But hey, it's good news that I've been doing more than necessary, now I can stop. :-) ----- Original Message ----- Subject: Re: which Onchecks ? Date: Fri, January 18, 2008 11:22 From: "Ben Thompson" <ben@nomonitorsoftspam.com> Floyd Wellershaus wrote: > > > This prompts me to ask myself, ( and you ) if they are really necessary > > and if so, which ones are definitely considered BEST PRACTICE to > > continue to do, and on what type of frequency ? > > I have to be honest and say that I was unaware that a good DBA was > supposed to run these on any regular basis at all. I though running > regular data integrity checks went out the window with C-ISAM. > > We look after about 50 servers, have done for some time and we never run > any onchecks as a precaution. We would only run one if a problem > developed or to cover all bases if there was a funny. Even then I have > rarely seen 'oncheck' find any errors, and on the rare occasions it has > that I can count on one hand, it can't fix them. We usually end up > dropping and recreating an index to fix it. > > No doubt someone else will tell us we're silly but we already irritate > our users enough with "update statistics" :-) > > I would be interested to hear from others about what they regard as best > practice. No doubt there is an element of judgement to this. > > Ben. > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > >

Floyd Wellershaus wrote: > This is good for me to hear. :-)) > Except for the part where I've been wasting time on them for so long. I > guess old habits die hard. <snicker> > One place where I'll never stop using them is before an upgrade. I've been > nailed on that before by the upgrade failing due to some corruption in a > systabauth that should have been seen and repaired before the upgrade. With upgrades I find it's also important to check that /tmp is not full and that your main database space has some free space. Maybe I should take something from you and run some onchecks beforehand. Generally though we have a HDR standby ready to take over if an upgrade fails on the primary. Ben.