Re: Benefits of reducing extents and running update stats

On 7 May, 10:02, "Obnoxio The Clown" <obno...@serendipita.com> wrote: > > > 3: I was a bit hesitant to add -y to the onchecks, but I figured what > > else could we do besides say Yes to the prompts. I can't imagine what > > else to do if there were problems detected, so I went with the -y option. > > Furry muff. :o) oncheck -cR oncheck -ce oncheck -cc <*** Missing oncheck -cID **for each database on the server** Do not add -y, the other option is for informix to dial in and fix the problem and this can make things harder for them to fix!

How would you go about running these oncheck statements on a database engine that can't stand an exclusive lock on a database table more than once a year? I have a number of databases that capture data from production systems and if the database is locked for a period larger than the buffers I have( around 5 minutes), data is lost. Thanks Jarrod Teale -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of david@smooth1.co.uk Sent: Tuesday, 8 May 2007 9:00 a.m. To: informix-list@iiug.org Subject: Re: Benefits of reducing extents and running update stats On 7 May, 10:02, "Obnoxio The Clown" <obno...@serendipita.com> wrote: > > > 3: I was a bit hesitant to add -y to the onchecks, but I figured what > > else could we do besides say Yes to the prompts. I can't imagine what > > else to do if there were problems detected, so I went with the -y option. > > Furry muff. :o) oncheck -cR oncheck -ce oncheck -cc <*** Missing oncheck -cID **for each database on the server** Do not add -y, the other option is for informix to dial in and fix the problem and this can make things harder for them to fix! _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list DISCLAIMER: This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email. You may not use, disclose or copy this email or its attachments in any way. Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group. http://www.fonterra.com/

On 7 May, 23:45, "Jarrod Teale" <Jarrod.Te...@fonterra.com> wrote: > How would you go about running these oncheck statements on a database > engine that can't stand an exclusive lock on a database table more than > once a year? > I have a number of databases that capture data from production systems > and if the database is locked for a period larger than the buffers I > have( around 5 minutes), data is lost. > > Thanks > Jarrod Teale > > Restore onto another machine and run onchecks on there. If you can only handle that little down time you must either - have enough money to be able to restore onto another machine - write the feeds into indentical databases on multiple machines and be able to take down one at a time. David.