RE: stupid -710 error again

Please, note, that along with 'alter table', -710 can be caused by the 'create/drop index' It is really interensting whether more recent versions of Informix are less sensitive to 'alter table' P.S. Don't tell me about 'set optimization low'. It doesn't help, if major version of the table is changed. ------------------------------------------ Alexey Sonkin > -----Original Message----- > From: rkusenet [mailto:rkusenet@sympatico.ca] > > IDS 9.21.UC4 > Solaris 2.6 > > This is puzzling. We got this -710 error in our production database > today. What is really surprising is that the instance was restarted > yesterday night. So the window of time during which the table would > have possibly been altered/renamed/dropped is within last 24 hrs. > > I googled and found no way to find out what was the time when the > table was last modified. Since all DDL statements are logged, > is there a way to look at the log files to see the SQL which > is the culprit here. > sending to informix-list

Alexey Sonkin <alexeis@grandvirtual.com> wrote in message news:<c8m2cu$1q3$1@terabinaries.xmission.com>... > Please, note, that along with 'alter table', > -710 can be caused by the 'create/drop index' > > It is really interensting whether more recent > versions of Informix are less sensitive to 'alter table' > > P.S. Don't tell me about 'set optimization low'. > It doesn't help, if major version of the table is changed. > > ------------------------------------------ > Alexey Sonkin Create/drop trigger on table does the same thing. This one, especially, has been a MAJOR pain as many of our tables are constantly open by one user or another or by our job scheduler, but I believe there's better behaviour in 9.4??????????? Malc