Table Creation on Primary Server
With HDR replication running (secondary read-only), creating a permanent table on the primary and then immediately loading data returned "ISAM error: the file is locked". Replies explained this is expected behaviour: when an index is created on the primary it must be shipped to the secondary as part of the commit, and the table/index stays exclusively locked until that transfer completes (messages appear in the online log). The workaround is simply to wait for the index replication to finish before touching the table; an IBM developer noted improvements were planned for a future release.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
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
I've seen this problem before. It normally appears after creating an index on a table on the primary. The table will be locked in exclusive mode until the index has been replicated across to the secondary. There will be a message in the online log stating that it's replicating the index and another one when it has finished. The only workaround seems to be to wait until the index has been replicated before you do anything else on the table. This is quite annoying when creating tables with several indexes within a script as the behaviour changes when dealing with an HDR primary. -- Message posted via http://www.dbmonster.com
I've seen this problem before. It normally appears after creating an index on a table on the primary. The table will be locked in exclusive mode until the index has been replicated across to the secondary. There will be a message in the online log stating that it's replicating the index and another one when it has finished. The only workaround seems to be to wait until the index has been replicated before you do anything else on the table. This is quite annoying when creating tables with several indexes within a script as the behaviour changes when dealing with an HDR primary. -- Message posted via DBMonster.com http://www.dbmonster.com/Uwe/Forums.aspx/informix/200609/1
dhaya.snidhi@gmail.com wrote: > 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.". I'm assuming that you are using HDR and not ER. With HDR, when an index is created on the primary, it must be transfered to the secondary. This transfer occurs as part of the commit. While this transfer occurs, the index is locked. We are doing work in the next release which I think should address this issue to a large degree. M.P. > > 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 >