By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,514 Members | 1,693 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,514 IT Pros & Developers. It's quick & easy.

Replication : when asn.IBMSNAP_UOW is pruned ?

P: n/a
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

Jun 23 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
rahul wrote:
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
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
Jun 28 '07 #2

P: n/a
On Jun 28, 6:56 am, Greg Nash <g...@namoicotton.com.auwrote:
rahul wrote:

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
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- Hide quoted text -

- 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.
Jun 28 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.