Re: Database features vs software replication

On May 4, 2017, at 3:40 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

Due to our legacy software we're not doing a whole lot of referential
integrity within the database itself. For example, do not allow an order
line created without a corresponding order header. Therefore we're not
using much (if any) foreign key constraints such as:

create table ordhead (
Ordernumber int as identity,
customernumber int,
primary key(ordernumber)
);

create or replace table ordline (
ordernumber int not null,
orderline int not null,
itemNumber int,
ordqty dec (15,5),
constraint ordline_ordheadFK foreign key (ordernumber) references ordhead
(ordernumber),
constraint ordlinePK primary key (ordernumber, orderline)
);

I've heard from someone that this can be problematic at times with
software based replication. I am trying to get clarification but I think
it had something to do with getting the order of the parent/child updates
reversed. This was causing an exclusive lock on the target causing them
to stop/restart their software based replication to clear the lock.
Sometimes as often as every other day.

Have others experienced such issues?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD