Same Offer Publication in Quick Succession Results in Pending Changeset
(Doc ID 2562273.1)
Last updated on JANUARY 27, 2022
Applies to:Oracle Communications Pricing Design Center - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Consider below scenario:
An offer with name '20014387' was published (row 7 in the database screenshot below) and in quick succession, the same offer was published as part of a larger XML (which included other offers as well, row 6 in the screenshot below):
From PricingAppServer.log, WebLogic indicates that the payload (changeset 1654233) is successfully published:
In transformation logs, there is no indication about this changeset (but the next changeset appears), no errors as well. It was just stuck in the WebLogic JMS queue itself. The larger changeset got synchronized to the transformer, but the row 7 changeset is now sitting in database as PENDING.
1. How/Why this can happen?
2. How to fix this pending changeset in the DB?
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