My Oracle Support Banner

BATCH_ORPOS_EXTRACT Failure Removes PricingExtract_*.xml Files (Doc ID 2500378.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Retail Merchandising System - Version 14.1 and later
Information in this document applies to any platform.

Symptoms

If the batch_orpos_extract.ksh [Control Process for Foundation Data Extracts for ORPOS] job fails due to any reason (example: locking), all temporary files are deleted including PricingExtract_*.xml which are generated by RPM batch.

When the failed job is rerun, the MOM*.jar gets generated with empty PricingExtract_*.xml file due to this behavior.


Steps to Reproduce:

  1. Ensure that the ORPOS PricingExtract_*.xml files have been generated by RPM.
  2.  Run batch_orpos_extract.ksh.
  3. After failure of batch_orpos_extract.ksh, re-run the job.
  4. Note that MOM*.jar contains an empty PricingExtract_*.xml file.

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.