My Oracle Support Banner

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

Last updated on DECEMBER 12, 2019

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:

> pt
> />index=0 gtrid=x0 x4a1514bd x20ed2f9
: Machine id: machine2, Transaction status: TMGABORTED
Group count: 2, timeout: 18000, time left: 3619
Known participants:
group: GR_CBA, status: TMGACTIVE, remote, coord
group: GR_NBN2, status: TMGABORTED, local

Machine id: machine, Transaction status: TMGABORTED
Group count: 3, timeout: 18000, time left: 3619
Known participants:
group: GR_CBA, status: TMGABORTED, local, coord
group: GR_NBN1, status: TMGABORTED, local
group: GR_NBN2, status: TMGABORTED, remote

Eventually aborted transactions accumulate in the GTT table over time, ultimately running out of
free GTT slots.   This is causing the following errors:


LIBTUX_CAT:328: ERROR: No space in Bulletin Board for Transaction Table
LIBTUX_CAT:397: ERROR: Cannot allocate entry on GTT
LIBTUX_CAT:1260: ERROR: Service request problem: _tmgadd

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

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