Re: Table not unlock after create index statement

Do you have Replication running ? If you do, that can and will cause a delay of the lock release while the change is getting sent over to the secondary. At least I've experienced that. If I had a big job to run, sometimes it was quicker and easier to turn off replication, run the jobs(s), and turn replication back on afterward. Even if it meant totally reestablishing replication from step 1. ======================== -<<Floyd Wellershaus>>- Database Administrator Unix Administrator email: fwellers@yahoo.com Home: 703-430-0805 Cell: 703-477-6045 ======================== http://www.one.org/ ----- Original Message ---- From: berso <berso1@gmail.com> To: informix-list@iiug.org Sent: Thursday, October 5, 2006 11:48:04 AM Subject: Table not unlock after create index statement This is kinda wierd, i'm programing with java, i create an index using a Statement.executeUpdate("CREATE INDEX..."), after that, i'm try to update the table and give me this error: update error :java.sql.SQLException: Table (infocorp.it_r38y39) has been dropped, altered or renamed. if i remove the CREATE INDEX the it runs fine, but way to slow, so i asuming that the table is not unlocking....any ideas? BTW already ask in the java group.....they send me here.... Thanks _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list