Oninit cdi / Archive
Talk to an expert →

ER: enterprise replication sync

Posted in 2012

Topics: High Availability & Replication, Installation, Setup & Upgrades, Error Codes & Troubleshooting, Server Administration, Migration, Import/Export & Data Conversion

Khaled Bentebal — — source: IIUG Forums & Mailing Lists

Hi, We are trying to migrate a database from one instance to another using ER in order to lower the downtime. The source database is on IDS 11.50 and the destination will be on 11.70.FC6 on a different machine; both use LINUX. We decided to first upgrade 11.50 to 11.70 to take advantage of ERKEY even if their creation is time consuming and locks the tables. We created ERKEY where Primary keys are missing. We defined both servers. We defines the replicates end even replicate sets. Synchronizing a single table works. Even synchronizing a replication set works with some problems when we used the option --process Since we want to migrate while the source server is in production (activity: deletes, upgrades, etc), I tried to simulate and did an update on a row on the source database and kept the lock (did not commit or rollback: used dbaccess with a begin work and without commit). When I run the sync, I get the following error and the sync stops: --------------------------------------------------------------------------- Starting synchronization scan for replicate fuel_referentiel_replicate Error returned from compareRepl: Execute statement: select count(*) from "informix".fuel_referentiel SQLCODE -252 ISAM -154 Error Details: 252: Cannot get system information for table. 154: ISAM error: Lock Timeout Expired Current Connection:conn2, Database:edilectre@g_primary command failed -- SQL failure (195) ---------------------------------------------------------------------------- We use CDR_DSLOCKWAIT 5 *How can run a sync while the server is running and be able to accomplish the migration with as little downtime as possible?* -- Cordialement, Regards, Khaled Bentebal Directeur Général - ConsultiX Président UGIF - User Group Informix France IIUG - Board of Directors Tél: 33 (0) 1 39 12 18 00 Fax: 33 (0) 1 39 12 18 18 Mobile: 33 (0) 6 07 78 41 97 Email: khaled.bentebal@consult-ix.fr Site Web: www.consult-ix.fr

↪ replying to Khaled Bentebal
Art Kagel — — source: IIUG Forums & Mailing Lists

Increase the lock timeout (CDR_DSLOCKWAIT) to say 10 seconds and don't manually hold locks an unnaturally long time just to test the sync! Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Wed, Nov 28, 2012 at 2:00 PM, Khaled Bentebal < khaled.bentebal@consult-ix.fr> wrote: > Hi, > > We are trying to migrate a database from one instance to another using > ER in order to lower the downtime. > > The source database is on IDS 11.50 and the destination will be on > 11.70.FC6 on a different machine; both use LINUX. > > We decided to first upgrade 11.50 to 11.70 to take advantage of ERKEY > even if their creation is time consuming and locks the tables. > We created ERKEY where Primary keys are missing. > We defined both servers. > We defines the replicates end even replicate sets. > > Synchronizing a single table works. Even synchronizing a replication set > works with some problems when we used the option --process > > Since we want to migrate while the source server is in production > (activity: deletes, upgrades, etc), I tried to simulate and did an > update on a row on the source database and kept the lock (did not commit > or rollback: used dbaccess with a begin work and without commit). > > When I run the sync, I get the following error and the sync stops: > --------------------------------------------------------------------------- > Starting synchronization scan for replicate > > fuel_referentiel_replicate > > Error returned from compareRepl: Execute statement: select count(*) from > "informix".fuel_referentiel > SQLCODE -252 ISAM -154 > > Error Details: > > 252: Cannot get system information for table.> > 154: ISAM error: Lock Timeout Expired> > Current Connection:conn2, Database:edilectre@g_primary > command failed -- SQL failure (195) > > ---------------------------------------------------------------------------- > > We use CDR_DSLOCKWAIT 5 > > *How can run a sync while the server is running and be able to > accomplish the migration with as little downtime as possible?* > > -- > Cordialement, Regards, > > Khaled Bentebal > Directeur Général - ConsultiX > Président UGIF - User Group Informix France > IIUG - Board of Directors > Tél: 33 (0) 1 39 12 18 00 > Fax: 33 (0) 1 39 12 18 18 > Mobile: 33 (0) 6 07 78 41 97 > Email: khaled.bentebal@consult-ix.fr > Site Web: www.consult-ix.fr > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --14dae9340ef12f8f3804cf9359b5

↪ replying to Khaled Bentebal
Celso Cabral Coimbra — — source: IIUG Forums & Mailing Lists

Khaled, I think creating each replicate separetely is esier, then you can control what to sync and when. It will be in your hand to control the migration. When creating replicates, which mode have you chose? by row or by transaction? You should choose by row. Celso Coimbra -----Mensagem original----- De: ids-bounces@iiug.org em nome de Khaled Bentebal Enviada: qua 28/11/2012 17:00 Para: ids@iiug.org Assunto: ER: enterprise replication sync [28943] Hi, We are trying to migrate a database from one instance to another using ER in order to lower the downtime. The source database is on IDS 11.50 and the destination will be on 11.70.FC6 on a different machine; both use LINUX. We decided to first upgrade 11.50 to 11.70 to take advantage of ERKEY even if their creation is time consuming and locks the tables. We created ERKEY where Primary keys are missing. We defined both servers. We defines the replicates end even replicate sets. Synchronizing a single table works. Even synchronizing a replication set works with some problems when we used the option --process Since we want to migrate while the source server is in production (activity: deletes, upgrades, etc), I tried to simulate and did an update on a row on the source database and kept the lock (did not commit or rollback: used dbaccess with a begin work and without commit). When I run the sync, I get the following error and the sync stops: --------------------------------------------------------------------------- Starting synchronization scan for replicate fuel_referentiel_replicate Error returned from compareRepl: Execute statement: select count(*) from "informix".fuel_referentiel SQLCODE -252 ISAM -154 Error Details: 252: Cannot get system information for table. 154: ISAM error: Lock Timeout Expired Current Connection:conn2, Database:edilectre@g_primary command failed -- SQL failure (195) ---------------------------------------------------------------------------- We use CDR_DSLOCKWAIT 5 *How can run a sync while the server is running and be able to accomplish the migration with as little downtime as possible?* -- Cordialement, Regards, Khaled Bentebal Directeur Général - ConsultiX Président UGIF - User Group Informix France IIUG - Board of Directors Tél: 33 (0) 1 39 12 18 00 Fax: 33 (0) 1 39 12 18 18 Mobile: 33 (0) 6 07 78 41 97 Email: khaled.bentebal@consult-ix.fr Site Web: www.consult-ix.fr ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Glossary