E1: 31A: R31802A Memory Issues Corrupt Data (8.11 thru 9.0 Bugs)

(Doc ID 1274651.1)

Last updated on NOVEMBER 17, 2016

Applies to:

JD Edwards EnterpriseOne Shop Floor Control - Version 8.11 Base to 9.0 [Release 8.11Base to 9.0]
JD Edwards EnterpriseOne Product Data Management - Version 8.11 Base to 9.0 [Release 8.11Base to 9.0]
Information in this document applies to any platform.
System Code: 31A - Manufacturing Accounting
Report: R31802A - Manufacturing Accounting Journal Entries


Symptoms

"No memory" error occurs when Manufacturing Accounting (R31802A) is run over large amounts of data.  The “No memory” error is displayed in the Work Center as the result of a memory leak.

Missing General Ledger records (F0911) may occur, and clearing of the Unaccounted Units (CTS1) from both the Work Order Parts List File (F3111) and the Work Order Detail File (F4801), can happen, making recovery impossible. 

The Work Center (P012503) also displays a 'No Memory' error.

Other symptoms include the following entries in the jde.log:

Sample Log #1

DB9900600 - Failed to store value, maximum exceeded.
Probable cause is forgetting to call jdeRemoveDataPtr()
.
CAC0001017 - (jdeCacheOpenCursor) failed to open cursor due
to reach the max #cursors (100) for cache (0B3xxxxxx-1)

OR
Sample Log #2

Thu Dec 16 10:25:17.142001 Jdb_ctl.c1782
JDB4100006 - DP - While freeing the JDB environment, leaked data pointer (08846890), pointer handle (1002), stored from File=b3104280.c, Function=I3104280CacheOpenCursor, Line=634.

 

3752/3020 WRK:Starting jdeCallObject
Thu Dec 16 10:25:17.158001 Jdb_ctl.c1782
JDB4100006 - DP - While freeing the JDB environment, leaked data pointer (00000000), pointer handle (1003), stored from File=b3104290.c, Function=I3104290CacheOpenCursor, Line=549.

 

3752/3020 WRK:Starting jdeCallObject
Thu Dec 16 10:25:17.158003 Jdb_ctl.c1815
JDB4100005 - Application code leaked 2 data pointers which were detected when freeing environment JSANDBOX (EnvHandle 01C610F0) for user JCHAFIN. Please refer to the debug log for details. If there are not enough details in the debug log to determine the cause, set DataPointerTracing=1 and Output=FILE in the [DEBUG] section of the JDE.INI and watch for this error message again. Or, set logDPLeaksAtSignoff=TRUE in the [DEBUG] section of the JDE.INI and look for JDB4100006 error messages. This message (JDB4100005) will only appear with debug tools code or when debug logging is turned on.

 

3752/3020 WRK:Starting jdeCallObject
Thu Dec 16 10:25:17.220002 ipcmisc.c299
API ipcSawUnregisterProcV1 : process 3752 unregistered in entry 15

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms