TMF Operations and Recovery Guide (G06.24+)

Occasional Operations
HP NonStop TMF Operations and Recovery Guide—522417-002
3-20
Controlling Individual Transactions
ALTER BEGINTRANS command with an AUTOABORT timeout value higher than
the present disconnect timer value.
The SNOOP utility is provided with the TMF product, and is documented in the file named
$SYSTEM.SYSnn.SNOOPDOC.
Controlling Individual Transactions
In certain rare cases, it may be necessary for you to manually cause a transaction to
complete. For transactions on local systems, you use the ABORT TRANSACTION
command to abort a transaction; for transactions on remote systems, you use the
RESOLVE TRANSACTION command to force a transaction to commit or abort. This
section discusses when you may need to take these actions.
You must be a member of the super user group to use the commands described in this
section (see the TMF Reference Manual for more information).
Aborting Transactions
The ABORT TRANSACTION command causes the effects of an active transaction to
be backed out, or causes the backout process to try again to back out an aborting or
hung transaction. It also releases the locks held by that transaction.
The following situations may require you to use the ABORT TRANSACTION command
to back out a transaction:
•
The backout process reports that it failed to back out a transaction. In this case, a
transaction goes from the aborting state to the hung state. Until a transaction
reaches the aborted state, the audit-trail files affected by the transaction remain
pinned in the audit trail. If the transaction remains hung, the audit trail can
eventually reach the begin-transaction-disable threshold. Also, records modified
by the transaction remain locked.
After the cause of the backout process failure is resolved, issue the ABORT
TRANSACTION command to cause the backout process to try again.
•
The autoabort function has been turned off and an excessively long-running
transaction is causing an overflow on the audit trail.
•
You have identified a transaction as runaway or invalid and do not want to wait for
the autoabort function to abort it.
•
A data volume cannot be restarted because all transactions pending on the system
have not been committed or aborted. Volume recovery is delayed until the
transactions are complete. It might be necessary to issue the ABORT
TRANSACTION command to abort long-running transactions.
Note. This problem occurs only if you change the disconnect timer setting from its default
value (30 seconds); that is, the AUTOABORT timeout value can be set lower than the dis-
connect timer value if the disconnect timer value is not changed from its default.