Re: sysviews corrupted

June Tong wrote: > > Guy Germonpre (germonpre_guy/dis@bekaert.com) wrote: > : Yes. In sequelink he is executing a macro. The macro does a connect, a > : drop table "extraction", then a create temp table "extraction", and then > : a lot of selects. > > : the macro is often executed, without problems, but it could be that the > : problems arise when the macro is executed many times without actualy > : leaving it. > > Pardon my ignorance, but what is sequelink, and what is a macro? > > Is this macro new? That is, you mentioned that the version you are > running (a fairly old version, by the way, but I never argue with success) > has been working for years, and suddenly started doing this; does that > correspond with adding this macro? > > I ask because this looks a little like the symptoms of an Informix bug > (sorry, can't find all the specifics right now) that occurred when you > try to use prepared statements against tables that have been dropped > (and possibly re-created) since the time you prepared the statement. > This was a very long time ago, but then, you're on a very old version :) > Basically, when you PREPARE a statement, it is parsed by the engine, > which includes translating the tablename to its partnum. When you drop > the table, even if you re-create it with the same name, the partnum is > no longer valid, therefore the prepared statement is no longer valid. Sequelink seems to be some kind of ODBC driver annex reporting tool, which permits you to execute a series of defined queries. It seems to me that you might be quite right. Those guys are doing some drops and recreates and it could well be that bug. thanks !