B2B 11g: Outbound Batching, Records with the Same Message ID Leaving One Record in MSG_WAIT_BATCH State
(Doc ID 1514918.1)
Last updated on MARCH 25, 2019
Applies to:Oracle B2B 10g (Business to Business) - Version 10.1.2.0.0 and later
Information in this document applies to any platform.
On B2B 220.127.116.11.0 version
In outbound batching, if two records with same message id are processed, one record is going out successfully while the other stays in MSG_WAIT_BATCH status.
Because they have the same message id, the primary key violation is thrown for the table B2B_PENDING_MESSAGE.
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