Integer
5
Purpose
The MaxWaitForQuietPoint parameter specifies the maximum time in seconds that the database waits for a quiet point in the following situations.
Quiescing the database for a quiesced backup or changing the access mode to archive.
Changing the access mode of a file to read‑only by using the
When locking files that are about to be reorganized. If a reorganization is audited, transactions are temporarily blocked and all files that are going to be reorganized are locked, allowing updating transactions to all files except those that are locked.
Performing an SDS take-over operation.
If the performing of one of these operations does not correspond to a natural quiet point, the MaxWaitForQuietPoint parameter specifies the maximum time in seconds that the database waits for existing transactions to complete before performing the operation after temporarily suspending new transactions from starting.
If a quiet point is not achieved within the time specified in this parameter, a DB_QUIETPOINT_TIMEOUT exception is raised.
Parameter is read when …
The database server node is initialized; for example, when you restart the database server.
Hints
The minimum value is zero (0) and the maximum value is 600 seconds (10 minutes).
Under a heavy transaction load, the waiting operation may not be possible when this parameter is set to the default value of zero (0), as a quiet point never occurs.
If you are waiting too long for an operation to be performed, use this parameter to force a quiet point so that the operation can take place.