Long interval without Checkpoint

My checkpoint is triggered each 300 seconds so how is possible this interval ? 18:42:00 Checkpoint Completed: duration was 0 seconds. 19:12:00 Checkpoint Completed: duration was 0 seconds. because there weren't any dirty pages ? (IDS 7.30) Thanks, Manel Falcó

Zero activity? In article <39982cd1.37131667@news.bcn.ttd.net>, manel@semic.es (Manel Falc' i Aige) wrote: > My checkpoint is triggered each 300 seconds so how is possible this > interval ? > > 18:42:00 Checkpoint Completed: duration was 0 seconds. > 19:12:00 Checkpoint Completed: duration was 0 seconds.> > because there weren't any dirty pages ? (IDS 7.30) > > Thanks, > Manel Falc' > > -- # unrm / ksh: unrm: not found # man cpio Sent via Deja.com http://www.deja.com/ Before you buy.

manel@semic.es (Manel Falc' i Aige) wrote: >My checkpoint is triggered each 300 seconds so how is possible this >interval ? > >18:42:00 Checkpoint Completed: duration was 0 seconds. >19:12:00 Checkpoint Completed: duration was 0 seconds. I think he means that the 1st checkpoint was conducted at 18:42 and the next won was 19:12. That's 30 minutes between the checkpoint interval. And he looks to be set at 5 minutes. ----------------------------------------------------------- Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free! http://www.keen.com

>I think he means that the 1st checkpoint was conducted at 18:42 >and the next won was 19:12. That's 30 minutes between the >checkpoint interval. And he looks to be set at 5 minutes. (Dang, why can't we edit our own posts?) I meant "the next one was 19:12." not won. ----------------------------------------------------------- Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free! http://www.keen.com

Manel Falcó i Aige <manel@semic.es> schrieb in im Newsbeitrag: 39982cd1.37131667@news.bcn.ttd.net... > My checkpoint is triggered each 300 seconds so how is possible this > interval ? > > 18:42:00 Checkpoint Completed: duration was 0 seconds. > 19:12:00 Checkpoint Completed: duration was 0 seconds.> > because there weren't any dirty pages ? (IDS 7.30) exactly !!! Regards Erik Stahlhut > > Thanks, > Manel Falcó >

manel@semic.es (Manel Falc' i Aige) wrote: >My checkpoint is triggered each 300 seconds so how is possible this >interval ? > >18:42:00 Checkpoint Completed: duration was 0 seconds. >19:12:00 Checkpoint Completed: duration was 0 seconds.> >because there weren't any dirty pages ? (IDS 7.30) > >Thanks, >Manel Falc' > A checkpoint will occur when the physical log becomes 75 percent full. If the physical log is too small, checkpoints will occur too often. A check point occurs at more or less regular intervals whenever there are active user threads in the instance. Factors that can cause a checkpoint to occur: - An amount of time = to CKPTINTVL seconds elapses without a checkpoint occuring. - 75% of physical log becomes full. - An onmode -c was issued. - Certain DB or instance commands, such as droping a chunk or changing the size or location of physical log, are issued. Manel, I know this did not answer your question precisely, but I would imagine that the _lack of_ all of the above criteria occurred and that's why the checkpoint did not occur. This may not have helped you - but it sure did me! I was wondering why my checkpoints didn't happen at exactly the prescribe time of 300 seconds, sometimes mine came sooner. ----------------------------------------------------------- Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free! http://www.keen.com