Home | Previous Page | Next Page   Logging and Log Administration > Managing Logical-Log Files > Setting High-Watermarks for Rolling Back Long Transactions >

Recovering from a Long Transaction Hang

If your system has ample disk space and you want to perform transactions of unknown length, consider setting LTXHWM to 100 to force the database server to continue adding log files until you complete the transaction.

A transaction might hang because the database server has run out of disk space. The database server stops adding new log files, writes an error message, and sets off an alarm.

To continue the transaction
  1. To continue the transaction, add a dbspace or chunk to a dbspace.
  2. Resume processing the transaction.

If you cannot add more disk space to the database server, end the transaction.

To end the transaction

When the database server comes up in fast-recovery mode, the transaction is rolled back. Then perform the following steps:

To recover from a long transaction hang
  1. Add more disk space or another disk until the transaction is successfully rolled back.
  2. Perform a point-in time restore to a time before the long transaction began or early enough for the database server to roll back the transaction.
  3. Drop the extra log files, dbspaces, or chunks from the database server instance.
  4. Perform a complete level-0 backup to free the logical-log space.
Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]