Re: Table Creation on Primary Server

Hi, not necessarily a bug. If you create a table with an index, then the index has to be replicated (i.e. also created) on the secondary. During this time on the primary there is a lock on the table. You can avoid the problem by setting "lock mode to wait" for the session that does the subsequent inserts. That way it will wait for the lock rather than immediately produce an error. In newer versions of IDS (from 10.00 I think) this index re-creation on secondary is optimized so that the chance to run in the lock is minimized. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management Informix URLs list: http://home.arcor.de/mfu1/informix/urls.html IBM Information On Demand Global Conference October 15-20, 2006, Anaheim, California see http://www.ibm.com/events/informationondemand informix-list-bounces@iiug.org wrote on 14.09.2006 07:49:10: > sounds like a bug, contact TS > > Superboer. > > dhaya.sni...@gmail.com schreef: > > > We have recently started Informix Replication. Our Secondary Server is > > in "Read Only" mode. We have a issue after doing this.When we create a > > permanent table on the Primary Server and try to load records into the > > table we get the following "ISAM error: the file is locked.". > > > > When we stop replication or create the same table temporarly we do not > > get the error. > > > > When we create a new Database in Primary server it does not give error > > and we can see the new DB in the Secondary Server. > > > > Is this normal for Primary server to not allow creation of permanent > > table in a replicated environment. > > > > Comments.. > > > > Dhaya > > Commercial Bank > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list