Re: Creation of a replicate
Posted in 2010
Topics: High Availability & Replication, Installation, Setup & Upgrades, Storage & Space Management, SQL Development & Query Writing, Server Administration, Security, Permissions & Auditing, Data Types & Schema Design
Hello!
Why don´t you try to run it using OAT?
It´s easier, faster, and you don´t worry about command lines.
Since you´re on 11.50 you already can do it.
I suggest you to try it, certainly it´s better than using some huge
command lines (old versions) ok?
Best regards!
Em 30/11/2010 12:08, Link, David A escreveu:
> We upgraded from 10.00.FC8 to 11.50.FC6. We had a replicate built on the following table:
>
> CREATE TABLE "informix".my_history (
> mydate VARCHAR(20,0),
> user CHAR(20),
> program CHAR(20),
> recordtype CHAR(20),
> data CHAR(255),
> mykey CHAR(20)
> ) WITH CRCOLS
> IN dbs1 EXTENT SIZE 1580 NEXT SIZE 156 LOCK MODE ROW;
>
> REVOKE ALL ON "informix".my_history FROM public;> CREATE UNIQUE INDEX "informix".uix_my_history ON "informix".my_history (
> mydate ASC,
> user ASC,
> program ASC,
> recordtype ASC,
> data ASC,
> mykey ASC
> ) USING btree IN dbs1;
>
> ALTER TABLE my_history ADD CONSTRAINT PRIMARY KEY (
> mydate,
> user,
> program,
> recordtype,
> data,
> mykey
> ) CONSTRAINT pk_history;>
>
> We had to rebuild the replicate and now it fails. The command which we used was:
>
>
> cdr define replicate -c grp200 -M grp200 -u -R --conflict=timestamp --scope=row my_db_my_history "my_db@grp200:informix.my_history" "select
> * from my_history" "my_db@grp229:informix.my_history" "select * from my_history"
> Verification of my_db@grp200:informix.my_history started
> Verification of my_db@grp200:informix.my_history is successful
> Verification of my_db@grp229:informix.my_history started
> Verification of my_db@grp229:informix.my_history is successful
> command failed -- unsupported SQL syntax (join, etc..) (40)
>
>
> We figured the "USER" column was causing the problem so we explicitly defined it with the table name prepended. Still didn't work.
>
>
> cdr define replicate -c grp200 -M grp200 -u -R --conflict=timestamp --scope=row my_db_my_history "my_db@grp200:informix.my_history" "select
> my_history.mydate, my_history.user, my_history.program, my_history.recordtype, my_history.data, my_history.mykey from my_history" "my_db@grp229:informix.my_history" "select my_history.mydate, my_history.user, my_history.program, my_history.recordtype, my_history.data, my_history.mykey from my_history"
> Verification of my_db@grp200:informix.my_history started
> Verification of my_db@grp200:informix.my_history is successful
> Verification of my_db@grp229:informix.my_history started
> Verification of my_db@grp229:informix.my_history is successful
> command failed -- unsupported SQL syntax (join, etc..) (40)
>
>
> Suggestions?
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
--
Alexandre Marini
Tecnologia da Informação - DBA
msn: alexandre_marini@hotmail.com
SEFAZ-MS / SGI-UGSR / Sistemas IBM-Informix
Cert-Info-Mgmt_color <Cert-Info-Mgmt_color.jpg>
IBM Informix Dynamic Server Certified Professional V10 / V11
On Nov 30, 11:28 am, Alexandre Marini <amar...@fazenda.ms.gov.br> wrote: > Hello! > Why don´t you try to run it using OAT? > > It´s easier, faster, and you don´t worry about command lines. > > Since you´re on 11.50 you already can do it. > > I suggest you to try it, certainly it´s better than using some huge > command lines (old versions) ok? > > Best regards! I fully agree with your suggestion that they use OAT. It makes ER much simpler to use. But the basic issue would not have been resolved by using OAT since replicates created by OAT are always mastered replicates.