 |
|
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. |
|
Copyright © 2011 Software Concepts International |