Replication : when asn.IBMSNAP

Replication : when asn.IBMSNAP_UOW is pruned ?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

rahul - 23 Jun 2007 20:54 GMT

i am testing my DB for replication.
Now 1 of the table AA is having large records and
during its delete the corresponding CD table is just getting piled
up .
since last 2 hrs the CD table is just increassing .
i have seen its transactions in IBMSNAP_UOW ,
now i want to force the pruning of IBMSNAP_UOW
and CDAA table . how to acheive that?
which parameters should i change so that even a major delete cope up
with
replication

Reply to this Message

Greg Nash - 28 Jun 2007 06:56 GMT

Pruning is performed by Capture, up to whatever point all known targets
have finished applying.
How many non-full-refreshing targets are defined, and have they all
caught up with the source data?

--g

> i am testing my DB for replication.
> Now 1 of the table AA is having large records and
[quoted text clipped - 7 lines]
> with
> replication

Reply to this Message

rahul - 28 Jun 2007 12:30 GMT

> Pruning is performed by Capture, up to whatever point all known targets
> have finished applying.
[quoted text clipped - 16 lines]
>
> - Show quoted text -

the Problem is just with one subscription set -TPPL
It has 5 tables in it.
One of the table gets major delete about 2 millions rows
the commit occours approx. after every deletion of 100,000 rows. The
whole delition takes approx. 3 Hrs on source
However it tooks about 9 hrs for replication to catch it up on Target
DB.

Reply to this Message