I have three apply sets and each set has its own apply process. Sometimes, usually once/twice daily all three apply processes will wait for 60 minutes before doing any work. In the apply log there will be 10 of these:

2009-11-05-12.46.11.929065 <CPREST(01/00)> ASN1044I APPLY "AQMINI3" : "WorkerThread". The Apply program will become inactive for "5" minutes and "0" seconds.

In the ASN.IBMSNAP_SUBS_SET table the LASTSUCCESS and LASTRUN column values are set 60 minutes ahead of the SYNCHTIME value.

APPLY_QUAL SET_NAME LASTSUCCESS SYNCHPOINT SYNCHTIME LASTRUN

AQDM LIQDM 11/4/2009 5:01:57.562309 PM 4AF1A9F5000000010000 11/4/2009 4:01:57.359817 PM 11/4/2009 5:01:57.562309 PM

AQMINI3 LIQ 11/4/2009 5:01:59.638186 PM 4AF1A9F5000000010000 11/4/2009 4:01:57.359817 PM 11/4/2009 5:01:59.638186 PM


Does anyone have any ideas why this is happening ? While this was happening I updated one of the tables and the apply processes still didn't caught up until the 60 minutes were over.

pns45d-0004:/app/home/db2inst1/replication/log> db2level
DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09053"
with level identifier "06040107".
Informational tokens are "DB2 v9.5.0.3", "special_21610", "U818976_21610", and
Fix Pack "3".
Product is installed at "/cs/IBM/db2/V9.5".

Solaris 10

It has been a while, but I believe that APPLY will go to sleep only when it believes it processed everything in CD/CCD tables and is completely caught up. There were some bugs around this early on but they should all have been taken care of by now. I also recall that there is a way to make APPLY more aggressive by reducing sleep time in config somewhere.

lastsuccess is the last run time - if nothing todo the synchpoint will not get increased I believe - apply will go to sleep for 5 min or the time defined for the qualyfier