Re: Problem locking table

----- Original Message ----- From: Obnoxio The Clown <obnoxio@hotmail.com> To: <candym@olcinc.com>; <informix-list@iiug.org> Sent: Friday, September 29, 2000 1:20 PM Subject: Re: Problem locking table > From: "Candy McCall" <candym@olcinc.com> > > > >We have a customer who just upgraded to > >Informix-4GL 7.30.UC4, Dynamic Server 9.21, Sun platform. > >They are using unbuffered logging and replication. > > > >We have a 4GL program that creates a table, creates an index > >on the table, then immediately attempts to place an exclusive > >lock on the table (LOCK table_name IN EXCLUSIVE MODE). > >An SQL error -289 is returned with ISAM error -113. The error > >message says the table is already locked, but how can that > >be if it was just created? Has anyone else experienced something > >such as this? > > Try doing a commit work after the create index. I thought the CREATE TABLE and CREATE INDEX statements did not need to be in a BEGIN/COMMIT WORK statement. The CREATE INDEX statement appears to be the culprit, so since the table is quite small anyway, we removed the CREATE INDEX statement and it appears to be working. Candy -- Candy McCall ONLINE Computing, Inc. (candym@olcinc.com)