RE: -710's in 24 x 7

Schedule regular periodic outages at the most convenient time. Most outages are not used. MW > -----Original Message----- > From: owner-informix-list@iiug.org > [mailto:owner-informix-list@iiug.org]On Behalf Of David E. Grove > Sent: Friday, 10 October 2003 8:37 a.m. > To: informix-list@iiug.org > Subject: -710's in 24 x 7 > > > IDS 9.21.FC4 > Solaris 8 > 24 x 7 > > We have a contractor provided Informix application. From > time to time, we > get updates from the contractor. Of course, these updates > typically include > table structure changes and stored procedure changes. We are > aware of only > two choices: > > > 1) permit users to remain connected while running UPDATE STATISTICS on > particular objects, which are identified from our error logs as users > encounter 710 errors (usually this quickly degenerates from targeting > specific objects, to just giving up and running UPDATE > STATISTICS on the > whole database, while users are connected, which further > inconveniences > users with 211 [sysprocplan] errors); > > 2) kick all users out first, then run UPDATE STATISTICS on the whole > database. > > > The problem is either method entails downtime for users. We > typically play > this game every quarter, sometimes more. > > The question is: how do other 24 x 7 shops maintain user > access while making > structural database changes to their application? > > Thank you. > > DG > > > > -- > David Grove > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - - - - > "I think not," said Descartes, and disappeared. > > sending to informix-list