cancel
Showing results for 
Search instead for 
Did you mean: 

replicating a PrimDB onto two RepDB, and one Table of same PrimDB onto a second RepDB, changing TbName

Former Member
0 Kudos

We have that situation:

One Ase Primary Database           Srv-P1      DB-1

Two Ase Replicate
Databases        Srv-R1      DB-1

                                   Srv-R2      DB-2  TB-ARC



The obective was to:

replicate all                from Srv-P1:DB-1  to    Srv-R1:DB-1

replicate A Specific
Table   from Srv-P1:DB-1(TB-DEV)

                             to   Srv-R2:DB-2(TB-ARC)

Of course, (TB-ARC) as
a different name as (TB-DEV)

also, 'DELETE' are
never replicated into (TB-ARC)

We created two RepDef:  database replication definition 'dd1'

                        table    replication definition 'td1'

       and two Subscr:  'ds1' mapped to 'dd1' replicating
Srv-P1:DB-1         into Srv-R1:DB-1

                        'ts2'
mapped to 'td2' replicating Srv-P1:DB-1(TB-DEV) into Srv-R2:DB-2(TB-ARC)

The problem is when we
are inserting a row into Srv-P1:DB-1(TB-DEV)

That should be
replicated in two places.

The replication is
correctly done by TableRepDef and Subscription 'td2'ts2' wher the 'mdl'
produced into de 'dsi' has been modyfied by the RepDef to fitt into Srv-R2:DB-2(TB-ARC).

Curiously, the
replication process try to replicate the same MDL into Srv-R1:DB-1(TB-ARC).

(TB-ARC) Table does not
exist Srv-R1:DB-1;
it exist only on Srv-R2:DB-2

The 'dsi' for
Srv-R1:DB-1 is shutting down with an error.

If we replace the
Database Replication Definition 'dd1' and is subscription 'sd1' by a set of
Tables Replication Definition and subscription for alle the Tables of
Srv-P1:DB-1, every goes well.

Each insert into
Srv-P1:DB-1(TB-DEV) is replicated into Srv-R1:DB-1 and Srv-R2:DB-2(TB-ARC)

Each insert into
others Tables of Srv-P1:DB-1(TB-DEV) is replicated into Srv-R1:DB-1

Accepted Solutions (1)

Accepted Solutions (1)

former_member182259
Contributor
0 Kudos

Dennis -

It was a bit hard to read the above due to formatting....and unfortunately, I don't speak French so some of the output that was attached was a bit beyond me....and the big issue was that the output didn't have the repdef RCL in it - which is the key part of the problem here.   However, I think I know what you are trying to do and wonder if you did it correctly.   What you should have done:

...let's assume we have a table named trades that in TB-ARC we want called trade_hist....

1) create repdef1 using the all tables clause with table named trades

2) create repdef2 using the primary table named trades and replicate table named trades_hist syntax

3) for the DSI connection to TB-ARC set the dsi_command_convert to d2none.....make sure you do this just for that connection (alter connection) vs. changing at the server level.

4) subscribe to repdef1 at the Srv-R1:DB-1

5) subscribe to repdef2 at TB-ARC

In the future, please provide ALL RCL scripts - specifically repdefs, subscriptions and any function string changes you have made.

Thanks!

Answers (0)