Re: ACE report - Help??

In article <8920@emory.mathcs.emory.edu>, ar@valstr.uucp (Andrew Roberts) writes: > > I have seen this error occurr in ESQL-C programs. In our case it > was due to someone running 'update statistics'. This updates some > of the data in the system catalogue, so the catalogue gets locked > for a while. This is why queries can't read them. > > This is a real problem for 24x7 sites. Informix say that you must > update statistics regularly or loose performance, but make it > impossible to do so without suffering. When we went to 4.1 OnLine from Turbo, I tried an update statistics on the db - this used to take a second, and now took about 40 minutes on an IDLE system - and yes, it TOTALLY locked the db, so badly that you could not even bring up the isql menu [for example]. Very nasty surprise. [I thought the db was corrupted]. The only work around is to run update statistics on each table in the db. This does not lock the entire db. [What I do is query for each non system table, put that into a list, and create an 'update statistics for table NAME;" for each NAME. I believe that Informix themselves is modifying the code that an updates statistics for the db will do this automatically [perhaps in 5.0 ???] Hope this helps, Ihor Kinal att!cbnewsh!ijk