My Oracle Support Banner

ORA-600 [504], ..., [Transaction Branch Allocation] Error When Using XA (Doc ID 868527.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.1 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 21-Jan-2014***

Symptoms

When using distributed transactions, next errors are raised in the alert log:

ORA-600 [504],..., [66], [6], [transaction branch allocation]


The trace file will show a call stack similar to the following:

... ksl_level_check kslgetl ktcsbr kpotxst kpotxsking kpotxen ...


The process state dump in the trace file will also show that the current session is already holding the 'transaction branch allocation' latch in module k2gget(), e.g.:

(latch info) wait_event=0 bits=42
holding (efd=4) 700000000026348 transaction branch allocation level=6
Location from where latch is held: ktccts.h LINE:592 ID:k2gget:before marking killed:
Context saved from call: 1152921504606827524
state=busy [holder orapid=70] wlstate=free [value=0]
holding (efd=4) 700000059e7f9a0 Child global tx hash mapping level=1 child#=23
...

Cause

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
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.