ER - inital data loading problems
Posted in 2006
Topics: High Availability & Replication, Storage & Space Management, Platform-Specific Issues, Versions, Editions & End-of-Life
Hello everyone. I'm setting up ER on three servers in primary-target mode. All servers run Linux kernel 2.6 (Debian, Suse SLES 9 and Redhat RHEL 4) and IDS 10.00 UC4. SLES and RHEL are setup exactly as machine notes say, and Debian is setup accordingly. At the moment it's only testing scenario, but the production system will be identical. I sucessfully initialized ER on all servers. Here is the output of cdr list server command: SERVER ID STATE STATUS QUEUE CONNECTION CHANGED ----------------------------------------------------------------------- g_debian 111 Active Local 0 g_redhat 311 Active Connected 0 Mar 13 12:05:36 g_suse 211 Active Connected 0 Mar 13 12:07:08 g_debian is primary server group, g_redhat and g_suse are targets After that I created stores_demo database on all servers, but deleted tables from stores_demo@g_suse and stores_demo@g_redhat because I wanted to test initial synchronization and loading the data. Now came template definition: cdr define template template_sd --conflict=ignore --master g_debian --ats --floatieee --ignoredel y --exclusive --all --database=stores_demo and then the realization of template, first for the primary... cdr realize template template_sd stores_demo@g_debian ...and then for the targets... cdr realize template template_sd --syncdatasource=g_debian --autocreate --dbspace <target_dbspace> --target stores_demo@g_suse stores_demo@g_redhat Both "cdr realize template" command were run on the primary server. The result is: everything's fine EXCEPT there are no rows in tables on targets. The tables got autocreated on targets but not populated with data. I suppose I made a mistake throughout the process, but after googling and RTFMing I didn't find where. Then I tried to synchronize the data "manually" with: cdr sync replicateset --master=g_debian --replset template_sd --all but I get error like this one: SYNC: Replicate template template_sd_ifxdebian_er_2_6_state is not active. Now I'm stuck here, waiting for any of your ideas... Thanks everyone!
Can I see the exact commands that you used? "Davorin Kremenjas" <davorin.kremenjas@alfatec.hr> wrote in message news:dv3pbu$1l2$1@ss405.t-com.hr... > Hello everyone. > I'm setting up ER on three servers in primary-target mode. > All servers run Linux kernel 2.6 (Debian, Suse SLES 9 and Redhat RHEL 4) and > IDS 10.00 UC4. > SLES and RHEL are setup exactly as machine notes say, and Debian is setup > accordingly. > > At the moment it's only testing scenario, but the production system will be > identical. > I sucessfully initialized ER on all servers. Here is the output of cdr list > server command: > > SERVER ID STATE STATUS QUEUE CONNECTION CHANGED > ---------------------------------------------------------------------- - > g_debian 111 Active Local 0 > g_redhat 311 Active Connected 0 Mar 13 > 12:05:36 > g_suse 211 Active Connected 0 Mar 13 > 12:07:08 > > g_debian is primary server group, g_redhat and g_suse are targets > > After that I created stores_demo database on all servers, but deleted tables > from stores_demo@g_suse and stores_demo@g_redhat because I wanted to test > initial synchronization and loading the data. > > Now came template definition: > cdr define template template_sd --conflict=ignore --master > g_debian --ats --floatieee --ignoredel > y --exclusive --all --database=stores_demo > > > and then the realization of template, first for the primary... > > cdr realize template template_sd stores_demo@g_debian > > > > ...and then for the targets... > > cdr realize template > template_sd --syncdatasource=g_debian --autocreate --dbspace > <target_dbspace> --target > > stores_demo@g_suse stores_demo@g_redhat > > > > Both "cdr realize template" command were run on the primary server. > > > > The result is: everything's fine EXCEPT there are no rows in tables on > targets. The tables got autocreated on targets but not populated with data. > > I suppose I made a mistake throughout the process, but after googling and > RTFMing I didn't find where. > > > > Then I tried to synchronize the data "manually" with: > > cdr sync replicateset --master=g_debian --replset template_sd --all > > > > but I get error like this one: > > SYNC: Replicate template template_sd_ifxdebian_er_2_6_state is not active. > > > > Now I'm stuck here, waiting for any of your ideas... > > > > Thanks everyone! > > > >
On thing.. You have to have realized the template on the source of the copy (g_debian). Also, be aware that the msg table in the stores DB has no primary key. You'll need to make sure that you put a PK on it before starting replicaiton. M.P. "Davorin Kremenjas" <davorin.kremenjas@alfatec.hr> wrote in message news:dv3pbu$1l2$1@ss405.t-com.hr... > Hello everyone. > I'm setting up ER on three servers in primary-target mode. > All servers run Linux kernel 2.6 (Debian, Suse SLES 9 and Redhat RHEL 4) and > IDS 10.00 UC4. > SLES and RHEL are setup exactly as machine notes say, and Debian is setup > accordingly. > > At the moment it's only testing scenario, but the production system will be > identical. > I sucessfully initialized ER on all servers. Here is the output of cdr list > server command: > > SERVER ID STATE STATUS QUEUE CONNECTION CHANGED > ---------------------------------------------------------------------- - > g_debian 111 Active Local 0 > g_redhat 311 Active Connected 0 Mar 13 > 12:05:36 > g_suse 211 Active Connected 0 Mar 13 > 12:07:08 > > g_debian is primary server group, g_redhat and g_suse are targets > > After that I created stores_demo database on all servers, but deleted tables > from stores_demo@g_suse and stores_demo@g_redhat because I wanted to test > initial synchronization and loading the data. > > Now came template definition: > cdr define template template_sd --conflict=ignore --master > g_debian --ats --floatieee --ignoredel > y --exclusive --all --database=stores_demo > > > and then the realization of template, first for the primary... > > cdr realize template template_sd stores_demo@g_debian > > > > ...and then for the targets... > > cdr realize template > template_sd --syncdatasource=g_debian --autocreate --dbspace > <target_dbspace> --target > > stores_demo@g_suse stores_demo@g_redhat > > > > Both "cdr realize template" command were run on the primary server. > > > > The result is: everything's fine EXCEPT there are no rows in tables on > targets. The tables got autocreated on targets but not populated with data. > > I suppose I made a mistake throughout the process, but after googling and > RTFMing I didn't find where. > > > > Then I tried to synchronize the data "manually" with: > > cdr sync replicateset --master=g_debian --replset template_sd --all > > > > but I get error like this one: > > SYNC: Replicate template template_sd_ifxdebian_er_2_6_state is not active. > > > > Now I'm stuck here, waiting for any of your ideas... > > > > Thanks everyone! > > > >
"Madison Pruet" <mpruet@comcast.net> wrote in message news:5LGdnZsQl8VROIjZnZ2dnUVZ_sKdnZ2d@comcast.com... > Can I see the exact commands that you used? Here they are: -- on primary server cdr define server --idle=500 --init g_debian -- on targets cdr define server --idle=500 --ats=<ats_dir> --sync=g_debian --init g_suse cdr define server --idle=500 --ats=<ats_dir> --sync=g_debian --init g_redhat -- on primary cdr define template template_sd --conflict=ignore --master g_debian --ats --floatieee --ignoredel y --exclusive --all --database=stores_demo cdr realize template template_sd stores_demo@g_debian cdr realize template template_sd --syncdatasource=g_debian --autocreate --dbspace datadbs --target stores_demo@g_suse stores_demo@g_redhat Here I checked targets and saw that tables were autocreated, but not populated with rows. Then I tried on primary: cdr sync replicateset --master=g_debian --replset template_sd --all and got this error: SYNC: Replicate template template_sd_ifxdebian_er_2_6_state is not active
"Madison Pruet" <mpruet@comcast.net> wrote in message news:SamdnVEp54ZAOojZRVn-tw@comcast.com... > On thing.. > You have to have realized the template on the source of the copy > (g_debian). Yes, I did that as mentioned in the other post. > Also, be aware that the msg table in the stores DB has no primary key. > You'll need to make sure that you put a PK on it before starting > replicaiton. I noticed that before trying to start the replication on targets. I dropped the table as the quickest solution.