TMF Management Programming Manual (G06.24+)

Commands and Responses
HP NonStop TMF Management Programming Manual—522420-002
5-73
DELETE TRANSACTION
for a long time. When the availability of these resources is more important than data
integrity, consider forcibly deleting the transaction.
If a transaction is in the hung or committed state, you can force its deletion by using
the DELETE TRANSACTION command. A hung transaction is one that TMF
attempted to abort but could not; a committed transaction is one that successfully
completed its changes to the database. (More about these and other transaction
states appears in the STATUS TRANSACTIONS command description.) As an
example, you can use a DELETE TRANSACTION command to remove a transaction
that was hung by the backout process because of audit reading errors; in fact, you can
only eliminate this transaction by forcibly removing it.
Usually, you will not manually alter the states of any transactions as the result of a
communications link failure. Transactions in the committed state cause no problems:
they do not hold database locks and they do not retain (pin) audit trail files on disk.
The only reason you might want to consider deleting a transaction from the committed
state is if the child node is destroyed and will never come back online.
Caution. DELETE TRANSACTION is a very dangerous command, because it can result in a
corrupted database. Use this command only with extreme caution. Alternative and safer
methods for forcibly deleting a transaction are provided by the RESOLVE TRANSACTION and
ABORT TRANSACTION commands, as noted elsewhere in this section of the manual.