Home |
Previous Page | Next Page Logging and Log Administration > Managing Logical-Log Files > Setting High-Watermarks for Rolling Back Long Transactions >
The exclusive-access, long-transaction high-watermark occurs when the long
transaction currently being rolled back is given exclusive access to the logical log. The database server dramatically reduces
log-record generation. Only threads that are currently rolling back transactions
and threads that are currently writing COMMIT records are allowed access to
the logical log. Restricting access to the logical log preserves as much space
as possible for rollback records that are being written by the user threads
that are rolling back transactions.
Warning:
If you set both LTXHWM and LTXEHWM to 100, long transactions are never stopped.
Therefore, you should set LTXHWM to below 100 for normal database server operations. Set LTXHWM to 100 to run scheduled transactions of unknown
length. Set LTXEHWM to 100 if you never want to block
other users while a long transaction is rolling back and you have ample disk
space.
Home |
[ Top of Page | Previous Page | Next Page | Contents |
Index ]