InjectorPriceEventBatch Performance Issue When Conflict Checking Large Volumes of Data
(Doc ID 1503693.1)
Last updated on FEBRUARY 06, 2019
Applies to:Oracle Retail Price Management - Version 22.214.171.124 to 13.2.6 [Release 13.2]
Information in this document applies to any platform.
Checked for relevance on 13-Feb-2015
When using the injectorPriceEventBatch to load, conflict check, and approve ~50,000 Item/Location Price Changes with the same item/locations appearing more than once (i.e., different dates), the performance of conflict checking and approval is very slow.
Steps to Reproduce:
1. Load RPM_STAGE_PRICE_CHANGE with 50,000 Item/Location price change records, each as a separate price change. Make sure the data is such that no conflicts will actually exist.
2. Make sure included in the 50,000 Item/Location price changes records are multiple instances of the same item/locations, with a price change for different dates.
For example, item #1 has 3 records for Store 1, each with a different date.
Additionally, make sure there is data that will conflict (i.e., price change already exists for item/location/date).
3. Make sure Logical Unit of Work (LUW) Count for conflict checking is set to 10,000.
4. Run the injectorPriceEventBatch.
5. Notice that the performance is very slow.
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