E1: 46: R46171 Crashes with Error JDB9900600 - Failed to Store Value, Maximum Exceeded (Doc ID 2800584.1)

Last updated on MAY 31, 2023

Applies to:

Symptoms

When the R46171 - Process Pick Requests is run in subsystem called from R46150 - Batch Picking Requests then after a while the R46171 crashes due to a memory leak. The jde.log shows error
JDB9900600 - Failed to store value, maximum exceeded. Probable cause is forgetting to call jdeRemoveDataPtr()
It appears that BSFN B4600380 - F4611VerifyAndGetSuggestion creates & stores datapointer which are not removed.
Note when running R46171 standalone from batch version the same issue can be observed as the logs shows error
JDB4100006 - DP - While freeing the JDB environment, leaked data pointer (09DFE138), pointer handle (1016), stored from File=b4600380.c, Function=F4611VerifyAndGetSuggestion, Line=494.

Steps to Duplicate:
1) Enter sales order for warehouse with 12 detail lines but do not create Pick request yet
2) From batch versions submit R46171, XJDE0007 to subsystem
3) P986113 shows R46171 subsystem job running
4) Set up R46150 to Create requests and process through subsystem and to call version XJDE0007 and then Run R46150 selection the order number
5) P4600: Note that Pick requests have been created and have been processed by R46171
6) P986113 end subsystem job and Note the data pointer memory leak in logs
JDB4100006 - DP - While freeing the JDB environment, leaked data pointer (09DFE138), pointer handle (1016), stored from File=b4600380.c, Function=F4611VerifyAndGetSuggestion, Line=494.
and
JDB4100005 - Application code leaked 11 data pointers which were detected when freeing environment JPD920
7) Enter another order and create Pick request through R46150 but do not call R46171
8) Run R46171 from batch version and note the same datapointer leak in logs

Cause

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