Unanswered: db2 apply processes sleeps for 60 minutes
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-22.214.171.1249065 <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.
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
Best Regards, Guy Przytula
Database Software Consultant
Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
Information Server Datastage Certified http://www.infocura.be