-289: Cannot lock table in requested mode

Posted in 2000

Topics: Transactions, Locking & Isolation

Ioannis Demetriades — Mon, 24 Jul 2000 09:38:56 +0300 — source: Informix-list mailing list archive (1991-1998)

Hi there, I am running a process in database transaction mode and due to the fact that the process was using up a lot of LOCKS (about 700,000) I decided to lock one of the tables in exclusive mode fearing that soon I would be running out of LOCKS. Begin Work; Lock Table Services In Exclusive Mode; ... Commit Work; I have a VB application that kicks off this process twice sequentially. The process has been running smoothly for quite a long time until yesterday when I got a 289 error message on the second call to this process and I have no clue as to why I got this error message. Don't the locks get released when you commit/rollback the work? Could it be that by the time the second process kicked off, informix had not managed to release all the locks ? I don't believe that anybody else was accessing the database at that time. PS: I am running this on Informix 7.31 UC2 on Sco Unix 5.05. Thanks -- Ioannis Demetriades CTL Ltd.

↪ replying to Ioannis Demetriades

David Williams — Mon, 24 Jul 2000 23:14:32 +0100 — source: Informix-list mailing list archive (1991-1998)

In article <397be598.0@news.spidernet.net>, Ioannis Demetriades <ioannis@ctl.com.cy> writes >Hi there, > >I am running a process in database transaction mode and due to the fact that >the process was using up a lot of LOCKS (about 700,000) I decided to lock >one of the tables in exclusive mode fearing that soon I would be running out >of LOCKS. > >Begin Work; >Lock Table Services In Exclusive Mode; >... >Commit Work; > >I have a VB application that kicks off this process twice sequentially. The >process has been running smoothly for quite a long time until yesterday when >I got a 289 error message on the second call to this process and I have no >clue as to why I got this error message. Don't the locks get released when >you commit/rollback the work? Yes. >Could it be that by the time the second process kicked off, informix had not >managed to release all the locks ? > No. Perhaps some other user was accessing the table at the time? >I don't believe that anybody else was accessing the database at that time. > >PS: I am running this on Informix 7.31 UC2 on Sco Unix 5.05. > >Thanks > >-- >Ioannis Demetriades >CTL Ltd. > > -- David Williams