LOB Data Missing From XA Transaction In Streams Replicated Environment
(Doc ID 1641866.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 11.2 to 12.1]
Information in this document applies to any platform.
LOB data is intermittently missing from Stream Apply sites when the source transaction is an XA transaction with branches in multiple nodes.
In this case we have two distinct tables into which data is inserted from two different branches of the same XA transaction where the branches are executed in different nodes. The LOB data appears in the source tables but in the replicated environment the LOB data for one of the tables is 0 bytes in size.
Analysis of the redo indicates that the LOB data is present in the redo logs for both inserts but it appears the COMMIT associated with the problem branch is not mined by the Capture process and so it believes the transaction to still be open and therefore the LOB data is not sent to the Apply.
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
|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.|