on 2014 Aug 13 3:50 PM
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
66 | |
10 | |
10 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.