E1: 31: Log Review Shows Batch Rate Close - R3191 Leaking Memory in Data Pointers When Calling BSFN VerifyAndGetWorkOrderMaster - B3100330 from BSFN UpdateWorkOrderStatus - B3100760 (Doc ID 2941104.1)

Last updated on APRIL 10, 2023

Applies to:

Symptoms

Batch Rate Close - R3191 updates the transactions correctly in the tables and there are no errors encountered on the screen. However, R3191 is leaking memory in data pointers and this is only visible in the logs.
When calling Business function VerifyAndGetWorkOrderMaster - B3100330 from UpdateWorkOrderStatus - B3100760, the following errors can be seen in the logs:
- JDB4100006 - DP - While freeing the JDB environment, leaked data pointer (0000000009D6FAD0), pointer handle (1002), stored from File=b3100330.c, Function=VerifyAndGetWorkOrderMaster, Line=186
and
- JDB4100005 - Application code leaked 1 data pointers which were detected when freeing environment JEUR926DV (EnvHandle 0000000000893f00)

The issue can be reproduced at will with the following steps:

1. BV: R3191 – Create a named version for R3191 UBE
2. Run R3191 version with debuglog activated for one order number where F4801T.MWDH > Blank
3. R3191 - Make sure the data selection is correct for R3191 so that the rate schedule can be closed
4. Open jde.log and jdedebug.log and search for data pointer leak:
   
   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.

Changes

Cause

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