HomeSearchSite MapContact Us

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

DATABASE
ADMINISTRATION

 
 

"Waiting For FREEZE" Stalls
TECHNICAL ARTICLES -> TROUBLESHOOTING ARTICLES
Back ] Next ] Printer Friendly Version ]

Q:

We experience many "Waiting for Freeze" stalls on our database. What are these and how can we eliminate them?

 

A:

A “Waiting for Freeze” stall occurs when Rdb or DBMS process fails and the RDMS/DBMS monitor creates a recovery process to roll-back the failed transaction. The freeze lock is a database-wide lock that is necessary to prevent other users from accessing these records until the recovery process can successfully roll-back the failed transaction. There are two ways to minimize the impact of freeze locks: reduce their frequency or reduce their duration. To reduce their frequency, you should avoid killing processes with STOP/ID or the use of idle process killers that perform a DELPRC (delete process) system service call; try using a FORCEX system service call first.

 

To reduce their duration, try the following: increase the number of recovery buffers available to the recovery process, increase the checkpoint frequency if you have fast commits enabled or disable the fast commit feature. If you have FAST COMMITS enabled on your database, reducing the checkpoint interval will also help.

 

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