Re: dropping tmp tables...

Since you say that you have to do a commit work before you can drop the temp table, I would guess that you are creating the table with transaction logging. If you add 'with no log' to the table creation statement (either create table or select into, whichever you are using), you should no longer have to do the commitwork. In general, you should always use with no log on temporary tables to improve performance of both your application and the database in general. Why invoke the overhead of logging on a table that is going to disappear as soon as your process ends? This will also eliminate the possibility of a long transaction being generated as a result of operations on your temporary table. Mr Cheuk Kong Lo wrote: > Running AIX 4.1..5 and ODS 7.23UC4 here. We have (think) we found a bug > in tmp tables. A few of our programs will reuse tmp tables, so upon end > of usage, we just drop the tmp tble. But we got error -242. The workaround > we have is to use commit work, then drop. then it is ok. Has > anyone come across similar problem? > > Thanks. > > -- > Chris Lo mailto: chris.lo@prudential.com.hk > System Administrator/Informix DBA mailto: cklo@cklo.hk.super.net > The Prudential Assurance (HK) Co. Ltd mailto: cklo@hk.super.net > ============================================================================== > -- Linux + FreeBSD + HPUX + Solaris + AIX > ============================================================================== > #include <std/disclaimer.h>