RP/TUX 8.1 In MP Mode, Aborted Transactions Stay In BBL Till Transactions Timeout (Doc ID 872492.1)

Last updated on JUNE 13, 2024

Applies to:

Oracle Tuxedo - Version 8.1 and later
Information in this document applies to any platform.

Aborted transactions remain in the BBL in TMGABORTED status even though the databases are okay with no outstanding locks.

The printtrans command in tmadmin shows:

There are no timeouts defined for tpbegin and these are long running transactions.

Introducing MAXTRANTIME to force aborted transactions entries to be removed from GTT does not resolve the issue. It just delays the issue.

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Symptoms

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.