HomeSearchSite MapContact Us

   RemoteDBA Services for CODASYL DBMS and Rdb Remote Management of OpenVMS Systems Preserving Mission Critical IT Applications Through Virtualization

DATABASE
ADMINISTRATION

 
 

Long Recovery Times with FAST COMMITS
TECHNICAL ARTICLES -> TROUBLESHOOTING ARTICLES
Back ] Next ] Printer Friendly Version ]

Q:

After enabling FAST COMMITS on our database, I noticed that the recovery times (and FREEZE LOCKS) have increased dramatically.  Is there something wrong?

 

A:

SCI clients have also experienced longer "freeze lock" delays when FAST COMMITS are enabled. This is a result of the transaction "redo" recovery needed when FAST COMMITS are implemented. If you are using FAST COMMITS and are experiencing excessive "freeze lock" delays, try reducing the checkpoint interval.

It is also a good practice to minimize the need for recovery processes by avoiding the use of "idle process killers" or STOP/ID. To terminate a database image, use the FORCEX system service rather than the DELPRC.

 

Top


Was this article helpful? 
This information and more was originally published in SCI's technical newsletter, DBAdvisor.
Past issues are available online; you may also fill out a subscription form.

If you have a technical question about this article or about any other 
CODASYL DBMS or Rdb topic, then ask our experts.

How would you rate this article?

5 (Highest)
4
3
2

0 (Did not apply)
Comments about this article or topic suggestions for new articles

Copyright © 2008 Software Concepts International
All Rights Reserved