---- original message from David R. Gilbert ----
*
* dtroutt@netcom.com (David Troutt) writes:
* :
* : Has anybody else seen this one? We are running Informix-OnLine V5.01 under
* : Solaris 2.2.
* :
* : A user creates a temp table and inserts into it. Later, the user drops the
* : temp table, but remains in his process (either ISQL or a 4gl program).
* : Another user now logs into the same database and tries to create a temp
* : table. This user either hangs (if he has SET LOCK MODE TO WAIT), or
* : generates the following error:
* :
* : SQL statement error number -261.
* : Cannot create file for table <tablename>.
* : SYSTEM error number -113.
* : ISAM error: the file is locked.
* :
* : We are pretty sure that the "drop table" statement does not release the
* : lock on the temp table, and when the 2nd user tries to create a temp table,
* : OnLine tries to use the same internal table name. It then sees the
* : leftover lock on the table, and either generates the error or makes the 2nd
* : process wait until the lock disappears. The lock, however, will not
* : release until the 1st process exits completely.
* :
* : I'd like to know if there is any way to fix this other than making sure we
* : never drop temp tables.
* :
* : Thanks in advance.
*
* Ahh, yes. We hit this one too. It is a known bug with 5.01.
* You need to upgrade to 5.02 and your problem will be fixed.
* It applies to all ports of OnLine 5.01 (SunOS 4.1.x, too.)
*
* Good luck!
*
* --
*
* - Dave
*
* David Gilbert Internet: doc@balr.com
*
If this problem has been fixed, there must be a bug number. Does anyone have
it?
We also are experiencing this problem in On-Line 4.10.UD3. Can anyone
explain why a temp table that no one else can access needs to be locked....
--
Jennifer Berak email: 4gen!warlok!jenb
Analyst/Project Manager jenb@sherwood.com
Sherwood Systems (A division of Sherwood Manufacturing) (602)230-8188
----------------------------------------------------------------------------