CDR -- define_serv -- synchronizing
User on IDS 7.24 could define the first Enterprise Replication server with the CDR API sample program define_serv, but adding a second server with the -S (synchronize) option failed with "cache define server, ID 1 collision failed (error 65)". An Informix developer explained that define_serv must connect (-c) to the instance being defined and that group names from sqlhosts, not server names, must be used, suggesting: define_serv -c grp2 -I -S grp1 grp2. That form gave error 44 (invalid database server name) on 7.24, so he offered the syntax he had used on that release (-c <groupid> <groupid> ... -I -S <sync_groupid>) and noted the NT cdr client is more forgiving, plus recommended upgrading to 7.31 for ER fixes. The thread ends without the poster confirming success, so no resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi! I have managed to declare one server to ER with CDR API sample program "define_serv" (IDS 7.24). But when I try to declare another server with SYNCHRONIZE option I get the following error message: CDR GC: operation cache define server, ID 1 collision failed (error 65). CDR GC: operation sync cache define remote server failed(error65). I have both database servers on the same machine, may that have an effect? I wasn't able to find further information from anywhere, so you are my "last hope". Your commend would be GREATLY appreciated. Best recards Katja Heikkinen Abacus Inc, Finland ps. I used the following commands: "define_serv -c g_server1 g_server1 -i 60 -s sndqdbs -r rcvqdbs -A /cdr/ats1 -R /cdr/ris1 -I" "define_serv -c g_server2 g_server2 -i 60 -s sndqdbs -r rcvqdbs -A /cdr/ats2 -R /cdr/ris2 -I -S g_server1" Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.
First of all - my pitch --- ;-) There have been a lot of fixes to ER since the 7.24 days. Please consider 7.31. OK - now for the problem.... You must be connected to the instance to use the define server. You need to use the "-c" option on the define server command to connect to that server. The define server works like a "request". Basically - I (server-xxx) want to join the enterprise. OK - suppose that you have two servers (serv1, and serv2) and the group entry in the sqlhosts file defines them as (grp1, and grp2). Then you would need to do the following: define_serv -c grp1 -I grp1 - That is: connect to grp1 and initialize ER on this server with the identity of grp1. (N.B. with ER always use the group name, not tht server name.) Later to define ER on the second instance - define_serv -c grp2 -I -S grp1 grp2 Or - connect to grp2 and initialize ER by syncing the global catalogur with grp1. This new entity will be called "grp2". katja.heikkinen@abacus-solutions.com wrote: > Hi! > > I have managed to declare one server to ER with CDR API > sample program "define_serv" (IDS 7.24). But when I try to declare > another server with SYNCHRONIZE option I get the following > error message: > > CDR GC: operation cache define server, ID 1 collision failed (error 65). > CDR GC: operation sync cache define remote server failed(error65). > > I have both database servers on the same machine, may > that have an effect? > > I wasn't able to find further information from anywhere, so you are > my "last hope". Your commend would be GREATLY appreciated. > > Best recards > Katja Heikkinen > Abacus Inc, Finland > > ps. I used the following commands: > > "define_serv -c g_server1 g_server1 -i 60 -s sndqdbs -r rcvqdbs -A > /cdr/ats1 -R /cdr/ris1 -I" > > "define_serv -c g_server2 g_server2 -i 60 -s sndqdbs -r rcvqdbs -A > /cdr/ats2 -R /cdr/ris2 -I -S g_server1" > > Sent via Deja.com http://www.deja.com/ > Share what you know. Learn what you don't.
Thank you for answering once again. The problem is that this syntax seems to cause another error message ("44 invalid database server name"). This occurs already when defining the first server. It seems like the sample application "define_serv" in 7.24 wanted the server name streight after the connect-clause, like "-c grp1 grp1". Is this possible by any means? The usage-clause of the sample program seems to refer to this type of syntax(???). But as I wrote this does not work either, because it causes the problem when trying to declare another server with sync option. Unfortanately, we are not able to upgrade to 7.3x at the moment. But do you think I would be more lucky, if I tried to define replication with NT client stuff?? Best Recards Katja Heikkinen In article <37962532.2EA93AAD@informix.com>, Madison Pruet <mpruet@informix.com> wrote: > First of all - my pitch --- ;-) > > There have been a lot of fixes to ER since the 7.24 days. Please consider > 7.31. > > OK - now for the problem.... > > You must be connected to the instance to use the define server. You need to > use the "-c" option on the define server command to connect to that server. > The define server works like a "request". Basically - I (server-xxx) want > to join the enterprise. > > OK - suppose that you have two servers (serv1, and serv2) and the group > entry in the sqlhosts file defines them as (grp1, and grp2). Then you would > need to do the following: > > define_serv -c grp1 -I grp1 - > > That is: > connect to grp1 and initialize ER on this server with the identity of grp1. > (N.B. with ER always use the group name, not tht server name.) > > Later to define ER on the second instance - > > define_serv -c grp2 -I -S grp1 grp2 > > Or - connect to grp2 and initialize ER by syncing the global catalogur with > grp1. This new entity will be called "grp2". > > katja.heikkinen@abacus-solutions.com wrote: > > > Hi! > > > > I have managed to declare one server to ER with CDR API > > sample program "define_serv" (IDS 7.24). But when I try to declare > > another server with SYNCHRONIZE option I get the following > > error message: > > > > CDR GC: operation cache define server, ID 1 collision failed (error 65). > > CDR GC: operation sync cache define remote server failed(error65). > > > > I have both database servers on the same machine, may > > that have an effect? > > > > I wasn't able to find further information from anywhere, so you are > > my "last hope". Your commend would be GREATLY appreciated. > > > > Best recards > > Katja Heikkinen > > Abacus Inc, Finland > > > > ps. I used the following commands: > > > > "define_serv -c g_server1 g_server1 -i 60 -s sndqdbs -r rcvqdbs -A > > /cdr/ats1 -R /cdr/ris1 -I" > > > > "define_serv -c g_server2 g_server2 -i 60 -s sndqdbs -r rcvqdbs -A > > /cdr/ats2 -R /cdr/ris2 -I -S g_server1" > > > > Sent via Deja.com http://www.deja.com/ > > Share what you know. Learn what you don't. > > Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.
Thank you for answering once again. The problem is that this syntax seems to cause another error message ("44 invalid database server name"). This occurs already when defining the first server. It seems like the sample application "define_serv" in 7.24 wanted the server name streight after the connect-clause, like "-c grp1 grp1". Is this possible by any means? The usage-clause of the sample program seems to refer to this type of syntax(???). But as I wrote this does not work either, because it causes the problem when trying to declare another server with sync option. Unfortunately, we are not able to upgrade to 7.3x at the moment. But do you think I would be more lucky, if I tried to define replication with NT client stuff?? Best Recards Katja Heikkinen In article <37962532.2EA93AAD@informix.com>, Madison Pruet <mpruet@informix.com> wrote: > First of all - my pitch --- ;-) > > There have been a lot of fixes to ER since the 7.24 days. Please consider > 7.31. > > OK - now for the problem.... > > You must be connected to the instance to use the define server. You need to > use the "-c" option on the define server command to connect to that server. > The define server works like a "request". Basically - I (server-xxx) want > to join the enterprise. > > OK - suppose that you have two servers (serv1, and serv2) and the group > entry in the sqlhosts file defines them as (grp1, and grp2). Then you would > need to do the following: > > define_serv -c grp1 -I grp1 - > > That is: > connect to grp1 and initialize ER on this server with the identity of grp1. > (N.B. with ER always use the group name, not tht server name.) > > Later to define ER on the second instance - > > define_serv -c grp2 -I -S grp1 grp2 > > Or - connect to grp2 and initialize ER by syncing the global catalogur with > grp1. This new entity will be called "grp2". > > katja.heikkinen@abacus-solutions.com wrote: > > > Hi! > > > > I have managed to declare one server to ER with CDR API > > sample program "define_serv" (IDS 7.24). But when I try to declare > > another server with SYNCHRONIZE option I get the following > > error message: > > > > CDR GC: operation cache define server, ID 1 collision failed (error 65). > > CDR GC: operation sync cache define remote server failed(error65). > > > > I have both database servers on the same machine, may > > that have an effect? > > > > I wasn't able to find further information from anywhere, so you are > > my "last hope". Your commend would be GREATLY appreciated. > > > > Best recards > > Katja Heikkinen > > Abacus Inc, Finland > > > > ps. I used the following commands: > > > > "define_serv -c g_server1 g_server1 -i 60 -s sndqdbs -r rcvqdbs -A > > /cdr/ats1 -R /cdr/ris1 -I" > > > > "define_serv -c g_server2 g_server2 -i 60 -s sndqdbs -r rcvqdbs -A > > /cdr/ats2 -R /cdr/ris2 -I -S g_server1" > > > > Sent via Deja.com http://www.deja.com/ > > Share what you know. Learn what you don't. > > Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.
Yes - the NT client is much more 'forgiving'. That's one of the reasons that we rewrote the cdr utility before we agreed to officially support it. The following format was what I used with 7.24 define_serv -c <groupid> <groupid> -A /tmp/ats_directory -R /tmp/ris_directory -I -S <sync_groupid> katja.heikkinen@abacus-solutions.com wrote: > Thank you for answering once again. > > The problem is that this syntax seems > to cause another error message ("44 invalid database server name"). > This occurs already when defining the first server. > > It seems like the sample application "define_serv" in 7.24 > wanted the server name streight after the connect-clause, > like "-c grp1 grp1". Is this possible by any means? The usage-clause > of the sample program seems to refer to this type of syntax(???). > But as I wrote this does not work either, because it causes the > problem when trying to declare another server with sync option. > > Unfortanately, we are not able to upgrade to 7.3x at the moment. > But do you think I would be more lucky, if I tried to define > replication with NT client stuff?? > > Best Recards > Katja Heikkinen > > In article <37962532.2EA93AAD@informix.com>, > Madison Pruet <mpruet@informix.com> wrote: > > First of all - my pitch --- ;-) > > > > There have been a lot of fixes to ER since the 7.24 days. Please > consider > > 7.31. > > > > OK - now for the problem.... > > > > You must be connected to the instance to use the define server. You > need to > > use the "-c" option on the define server command to connect to that > server. > > The define server works like a "request". Basically - I (server-xxx) > want > > to join the enterprise. > > > > OK - suppose that you have two servers (serv1, and serv2) and the > group > > entry in the sqlhosts file defines them as (grp1, and grp2). Then you > would > > need to do the following: > > > > define_serv -c grp1 -I grp1 - > > > > That is: > > connect to grp1 and initialize ER on this server with the identity of > grp1. > > (N.B. with ER always use the group name, not tht server name.) > > > > Later to define ER on the second instance - > > > > define_serv -c grp2 -I -S grp1 grp2 > > > > Or - connect to grp2 and initialize ER by syncing the global catalogur > with > > grp1. This new entity will be called "grp2". > > > > katja.heikkinen@abacus-solutions.com wrote: > > > > > Hi! > > > > > > I have managed to declare one server to ER with CDR API > > > sample program "define_serv" (IDS 7.24). But when I try to declare > > > another server with SYNCHRONIZE option I get the following > > > error message: > > > > > > CDR GC: operation cache define server, ID 1 collision failed (error > 65). > > > CDR GC: operation sync cache define remote server failed(error65). > > > > > > I have both database servers on the same machine, may > > > that have an effect? > > > > > > I wasn't able to find further information from anywhere, so you are > > > my "last hope". Your commend would be GREATLY appreciated. > > > > > > Best recards > > > Katja Heikkinen > > > Abacus Inc, Finland > > > > > > ps. I used the following commands: > > > > > > "define_serv -c g_server1 g_server1 -i 60 -s sndqdbs -r rcvqdbs -A > > > /cdr/ats1 -R /cdr/ris1 -I" > > > > > > "define_serv -c g_server2 g_server2 -i 60 -s sndqdbs -r rcvqdbs -A > > > /cdr/ats2 -R /cdr/ris2 -I -S g_server1" > > > > > > Sent via Deja.com http://www.deja.com/ > > > Share what you know. Learn what you don't. > > > > > > Sent via Deja.com http://www.deja.com/ > Share what you know. Learn what you don't.