Was this helpful?
Aborting Transactions
At any time before an end transaction statement commits an MQT, the transaction can be aborted, either by the application program (using an abort statement) or by the DBMS Server (under specific circumstances). When a transaction is aborted, all effects of the transaction on the database are rolled back. No other transactions in progress are adversely affected.
MQTs can be aborted in the following ways:
Program abort
Specifies that the QUEL statement abort terminates an MQT
Log file too full
Specifies that when the log file becomes too full (80% is the default), the DBMS Server begins to abort the oldest transactions to free up space in the log file. (To avoid forced aborts, allocate sufficient space for the log file.)
Deadlock
Specifies that when the DBMS Server detects deadlock, it aborts one transaction to end the deadlock. For an explanation of deadlock, see Deadlock: Detection, Avoidance, and Handling.
Exit statement
Specifies that exiting the database with an EQUEL exit statement aborts any in-progress MQT
Last modified date: 06/10/2024