If a replicate is created with the --erkey for example :
cdr define replicate --conflict=ignore --ats --ris rep_mytab
--erkey \'
"testdb@g_serv1:informix.mytab" "select t.col1, t.col2, t.col3,
t.col4, t.new_col2, t.new_col3, t.new_col4, t.col5 from mytab t"
\'
"testdb@g_serv2:informix.mytab" "select t.col1, t.col2, t.col3,
t.col4, t.new_col2, t.new_col3, t.new_col4, t.col5 from mytab t"
and the above replicate 'rep_mytab' is deleted and rebuild with
the output of 'cdr list catalog -r', for example :
$ cdr list catalog -r
#
# cdr define replicate commands.
#
cdr define replicate --conflict=ignore --ats --ris rep_mytab \'
"testdb@g_serv1:informix.mytab" "select t.ifx_erkey_1,
t.ifx_erkey_2, t.ifx_erkey_3, t.col1, t.col2, t.col3, t.col4,
t.new_col2, t.new_col3, t.new_col4, t.col5 from mytab t" \'
"testdb@g_serv2:informix.mytab" "select t.ifx_erkey_1,
t.ifx_erkey_2, t.ifx_erkey_3, t.col1, t.col2, t.col3, t.col4,
t.new_col2, t.new_col3, t.new_col4, t.col5 from mytab t"
it fails with following error :
Interpreting this replicate as a master replicate.Table
'testdb@g_serv1.adj_detail' does not contain primary key.
it happens because 'cdr list catalog -r' does not include the
option "--erkey" but only the ifx_erkey shadow columns.
If --erkey is added to the output of 'cdr list catalog -r' for
example :
cdr define replicate --conflict=ignore --ats --ris rep_mytab
--erkey \'
"testdb@g_serv1:informix.mytab" "select t.ifx_erkey_1,
t.ifx_erkey_2, t.ifx_erkey_3, t.col1, t.col2, t.col3, t.col4,
t.new_col2, t.new_col3, t.new_col4, t.col5 from mytab t" \'
"testdb@g_serv2:informix.mytab" "select t.ifx_erkey_1,
t.ifx_erkey_2, t.ifx_erkey_3, t.col1, t.col2, t.col3, t.col4,
t.new_col2, t.new_col3, t.new_col4, t.col5 from mytab t"
the above commands works successfully and the replicate is
created. |
