Primary / foreign key replication

[jmtorres]

Good Day,

Suppose  we have a Warm Standby , ASE 15.5, RS 15.6 with several databases pairs and table cross reference between these different databases, i.e:

Pdb1 -> Stdby1

Pdb2 -> Stdby2

..--.........

PdbN -> StdbyN

Table T1 is at Pdb1 , table T2 is at Pdb2

T1 has  a Pkey  , T2 has  a Fkey  to PKey on T1( for example a master / detail relation ship) 

and so on

Some times due to network latency (or other event)  table T2 gets replicated before than T1 and replcation stops due to primary constraint violation, even though the PK exists on T1 ( but hasn't been replicated yet).

Q: Is there any way to ensure that T1 would get replicated first in order to avoid the error?

Thank you

Regards

Jose-Miguel

[jmtorres]

Mark,

Thank you very much

Regards

JM

[luc_vanderveurst · Accepted solution]

What would help is that SAP implements a 'set check_constraints off' command,

just like there exists a 'set triggers off' or 'set replication off' command.

The replication server could then execute this command just like it

executes set triggers off when doing warm standby or msa replication.

Luc.

[former_member182259 · Accepted solution]

ASE 15.7 ESD #2:

set disable_ri_check [ on | off ]

Added from CR 655851.....    requires replication_role.