My Oracle Support Banner

Allocation Calculation Error - "The Allocation could not be saved. Try again later." (Doc ID 2858289.1)

Last updated on JULY 19, 2022

Applies to:

Oracle Retail Allocation Cloud Service - Version 19.3 and later
Information in this document applies to any platform.

Symptoms

When trying to use the allocation module to create an allocation for item list with 150 or 450 items from a location list and a store list, the calculation keeps failing with an error that says "The Allocation could not be saved. Try again later."

Below error is seen in the server log:

[2022-03-23T22:29:59.785+00:00] [alloc-server_1] [ERROR] [] [oracle.retail.apps.alc.model.core.util.AllocException] [tid: [STUCK].ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: RETAIL_ASYNC_TASK_USER] [ecid: ,,0:1] [APP: allocamc] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: ] ERRMSG_ALLOC_SAVE_ALLOC_ERR[[
java.sql.BatchUpdateException: ORA-00001: unique constraint (RMS01.ALC_ITEM_LOC_I1) violated

at oracle.jdbc.driver.OraclePreparedStatement.executeLargeBatch(OraclePreparedStatement.java:9775)
at oracle.jdbc.driver.T4CPreparedStatement.executeLargeBatch(T4CPreparedStatement.java:1448)
at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:9540)

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
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.