Specifies the name of the database where you are enabling or disabling a quiet processing point.
enable | disable
Enables or disables a quiet processing point. Any processes that attempt transactions while a quiet point is enabled must wait until the quiet point is disabled.
nolock
Allows you to enable a quiet point without waiting on shared memory latches.
markbackedup
Allows you to mark the database as backed up as the quiet point ends.
bithreshold n
Specifies the maximum size to which BI recovery files can grow, where n is an integer specifying the size of the threshold in MB. You can increase the size of the threshold above the current value or reduce the size to one cluster larger than the size of the recovery log file at the time the PROQUIET command is issued.
Note: Though the above table lists the -C parameter to show the complete syntax, you do not need to use the -C parameter in the PROQUIET syntax.
PROQUIET ENABLE stops all writes to the database; PROQUIET DISABLE ends the quiet point to resume writes. PROQUIET is useful for advanced backup strategies. You can also use the PROQUIET command with the bithreshold parameter to adjust the size of the recovery log threshold online. Use the PROSERVE command with the -bithold startup parameter to set the size of the primary recovery log threshold on startup.
Enabling a quiet point on a database with after-imaging enabled forces an AI extent switch.
Enabling a no-lock quiet point on a on a database with after-imaging enabled does not force an AI extent switch. The BUSY AI extent at the time the no-lock quiet point is enabled must be rolled forward with ROLL FORWARD RETRY. For more information, see RFUTIL ROLL FORWARD RETRY qualifier
Disabling a quiet point with the markbackedup option marks the database in the same manner as the RFUTIL MARK BACKEDUP command, but allows the database to stay online. For more information on the RFUTIL command, see RFUTILMARK BACKEDUP qualifier.
Quiet points are only available on Enterprise systems.
Example
Use the PROQUIET command to manage the primary recovery area (BI) threshold before your database stalls.
For example, to start a server and set a 500MB BI threshold, allowing the system to stall if that threshold is reached, use the PROSERVE command as follows:
proserve mydemo -bithold 500 -bistall
Assume a long running transaction causes the expansion of the BI, but before the threshold is reached you receive the following message:
BI file size has grown to within 90% of the threshold value 523763712.
(6559)
After receiving message 6559, you decide to increase the BI threshold to 1GB while the database remains online and investigate the cause of the unexpected BI growth before the system stalls. Use the PROQUIET command, as follows:
proquiet mydemo bithreshold 1000
The above command establishes a quiet point and increase the threshold. The database does not stall.
Note: In practice, invoke PROQUIET commands by using a script so that they occur as quickly as possible and with the least amount of impact to the online system.
When a database stalls because the BI threshold is reached, the stall causes an implicit quiet point and the database engine writes a message to the log file. To expand the BI threshold and continue forward processing, use the PROQUIET command with the bithreshold parameter only, as follows:
Enabling a quiet point on a database with after-imaging enabled forces an AI extent switch.