Enterprise Replication with a Stored Procedure Conflict Resolution
Posted in 2000
Topics: High Availability & Replication, Stored Procedures & SPL, Platform-Specific Issues, Versions, Editions & End-of-Life
Can anyone tell me what I am doing wrong here?
IDS 7.31
HP-UX 11.0
We are using update anywhere replication for 1 table between 2 servers.
The conflict resolution is defined as an Optimized Stored Procedure ( -O
flag ). My problem is that is seems that the first 2 parameters
(targetServer and targetTS) are always set to NULL. I know that if a row
with the same primary key does not exist on the target server then these 2
parameters will be NULL, but I have verified that these rows exist on the
target server and they are still passed as NULL. Thanks in advance for any
help that anyone can offer.
create procedure pin_mast_ER_SP (
targetServer char(18), targetTS datetime year to second,
targetDeleted char(1),
sourceServer char(18), sourceTS datetime year to second,
sourceDbop char(1),
t_pin char(16), t_dnis.......
targetServer and targetTS always seem to be NULL.
I'm guessing that you are using SP only for conflict resolution and not
timestamp + SP. That being the case, I'm guessing that you are running into
this just after having copied the data from the source to the target instance.
The NULL is the default value for the two CRCOLS. So that would represent the
values just after the SYNC.
Andrew Ford wrote:
> Can anyone tell me what I am doing wrong here?
>
> IDS 7.31
> HP-UX 11.0
>
> We are using update anywhere replication for 1 table between 2 servers.
> The conflict resolution is defined as an Optimized Stored Procedure ( -O
> flag ). My problem is that is seems that the first 2 parameters
> (targetServer and targetTS) are always set to NULL. I know that if a row
> with the same primary key does not exist on the target server then these 2
> parameters will be NULL, but I have verified that these rows exist on the
> target server and they are still passed as NULL. Thanks in advance for any
> help that anyone can offer.
>
> create procedure pin_mast_ER_SP (
> targetServer char(18), targetTS datetime year to second,
> targetDeleted char(1),
> sourceServer char(18), sourceTS datetime year to second,
> sourceDbop char(1),
> t_pin char(16), t_dnis.......>
> targetServer and targetTS always seem to be NULL.