Problem locking table

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? Thanks for any insight! Candy -- Candy McCall ONLINE Computing, Inc. (candym@olcinc.com)

Replication maybe causing this. I know when building indexes. If we try to build several indexes in a row, the second one will fail. We have to set lock mode to wait. The lock is freed after the index is replicated. This would probably happen on a create table as well. Candy McCall wrote: > > 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? > > Thanks for any insight! > > Candy > -- > Candy McCall > ONLINE Computing, Inc. > (candym@olcinc.com)