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 OCTOBER 25, 2016

Applies to:

Oracle SOA Platform – B2B (Business to Business) - Version to [Release 11gR1]
Information in this document applies to any platform.


On B2B 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.




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms