Friday, December 16, 2011

How to guage approximate time for the replicat to catchup the long running transactions

An instance is when running any batch job which has some long running transactions you would want to know an estimate on how long it will take to propogate these on target database.

Basically, we will need to check the replicat report to see how many minutes it is taking to finish processing a trail. Now multiply this time into the number of remaining trail files which the replicat has to process.

For example, in the report file:

Opened trail file ./dirdat/vv001401 at 2011-12-16 16:13:16

---
---
---

Switching to next trail file ./dirdat/vv001402 at 2011-12-16 16:43:18 due to EOF, with current RBA 499999734
Opened trail file ./dirdat/vv001402 at 2011-12-16 16:43:18

This took almost 30 minutes for processing. Now multiply 30 with the remaining trail files number and this should give a rough extimate of time for the replicat to process. We should also consider the trail files getting populated from source to the target machine and we need to anticipate time for that as well.


No comments:

Post a Comment