All open transactions are suspended when the transaction log reaches the last-chance threshold. Typically, space is created by dumping the transaction log, since this removes committed transactions from the beginning of the log. However, if one or more transactions at the beginning of the log is still open, it prevents a dump of the transaction log.
Use lct_admin abort to terminate suspended transactions that are preventing a transaction log dump. Since terminating a transaction closes it, this allows the dump to proceed. Figure 16-5 illustrates a possible scenario for using lct_admin abort:
Figure 16-5: Example of when to use of lct_admin abort
In Figure 16-5, a transaction log has reached its LCT, and open transactions T1 and T6 are suspended. Because T1 is at the beginning of the log, it prevents a dump from removing closed transactions T2 through T5 and creating space for continued logging. Terminating T1 with lct_admin abort allows you to close T1 so that a dump can clear transactions T1 through T5 from the log.
lct_admin abort replaces lct_admin unsuspend.
