Performance Issue on Conflict Check Performed for PriceEventInjector Batch
(Doc ID 1954040.1)
Last updated on OCTOBER 14, 2018
Applies to:Oracle Retail Price Management - Version 13.2.4 and later
Information in this document applies to any platform.
Checked for relevance on 12-May-2017
This article will be updated as official patch information becomes available.
The Price Injector batch conflict check process never ends. One needs to kill the process manually. There were not many item/location records to inject via stage tables: 5095 price change item/loc, 2000 simple promotions records were tried to inject, but the process never ended and users had to kill it.
Steps to Reproduce:
1. Load data into stage tables like RPM_STAGE_CLEARANCE and RPM_STAGE_PROMO_COMP_SIMPLE tables.
2. Run RPM.INJECTORPRICEEVENTBATCH batch with appropriate parameters (PC or SP).
3. Notice that this process keeps conflict checking and never returns.
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