Oracle Retail Merchandising Foundation Cloud Service Oracle Retail Pricing Cloud Service Oracle Retail Invoice Matching Cloud Service Oracle Retail Allocation Cloud Service Information in this document applies to any platform.
Purpose
This troubleshooting guide lists the common batch failure or long running scenarios in Merchandising and provides recommended troubleshooting and resolution steps for specific errors.
There are times when batch jobs may fail with errors. This can be due to a number of reasons such as, incorrect data setup, incorrect file structure, locking issues or they can also run longer than expected depending on data volume or any other issue. When these exceptions happen, action/intervention may be required to recover and complete the batch job.
Many of the batch exception cases can be resolved on the retailer’s end without raising a service request with Oracle by referring to this guide for common exception scenarios. This provides control and flexibility for customers to resolve batch errors in real time.
For the batch job errors that are not mentioned in this guide, a customer may raise service request with Oracle to get help with resolving the error.
For batch exception scenarios that require data cleanup for resolution, the customer should raise service request with Oracle for their "production environment" as data correction is restricted via Apex Dataviewer. For non-production environments, however, the customer must clean up data via the Apex Dataviewer.
Troubleshooting Steps
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
