My Oracle Support Banner

E1: BSFN: Case Study on Memory Violation, Memory Corruption, Memory Overwrite, Access Violation and Zombie Kernel Caused by Standard Business Functions (Doc ID 1464687.1)

Last updated on FEBRUARY 28, 2018

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Purpose

Note: If you encounter business function error while using standard application or UBE, it maybe already reported, install ESU for fix. If issue has not been reported, open service request with team that support the application or UBE, example, select product JD Edwards EnterpriseOne Sales Order Management while opening a SR if encountering business function issue while using P4210.
If you encounter issue with standard business function used in custom object (application or UBE), check if issue also appear with standard application or UBE. If issue does not appear, most likely there is no bug with the standard business function.

 

The purpose of this document is to explain in high level, some memory issues encountered in running standard business functions through the CallObject Kernel in EnterpriseOne. This document includes case studies and resolutions on certain memory issues. This document is not intended to cover specific definition on memory errors or how to detect memory problems.

This document is intended to help internal JDE developer on what to check when hitting memory errors in EnterpriseOne and how to apply possible fix for these errors while working on reported bug. But information in this document maybe helpful for developing custom business function.

The audience for this document is someone with expert 'C' Programming Language development knowledge. This document only contains examples. It is not meant to be all encompassing. Also see the second document in this series <Document 1554611.1> E1: BSFN: Case Study on Memory Violation, Memory Corruption, Memory Overwrite, ACCESS VIOLATION and Zombie Kernel Caused by Standard Business Functions Part 2.

This document does not cover any memory corruption issues caused by the Tools Foundation Layer which is usually fixed through tools release upgrade. This document mainly focuses on memory errors caused by standard business functions which results in CallObject Kernels to crash or runbatch application to fail.

Caution: This document may contain information, software, products or services which are not supported by Oracle Support Services and are being provided ‘as is’ without warranty. Please refer to the following site for My Oracle Support Terms of Use: https://support.oracle.com/CSP/ui/TermsOfUse.html.  For custom business function, field services may need to be engaged.

 

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!


In this Document
Purpose
Troubleshooting Steps
 Memory Error
 Memory Leak
 Memory Corruption and Example:
 Memory Diagnostic Tools in EnterpriseOne:
 Case Study in Interactive Application:
 Memory violation in Batch Application:
 Open Table Not Closed:
 Function Cleanup:
 JDB_FreeEnv()
 JDE INI Parameters which ease you to debug:
 Other issues - Max Cursor and Max Data Pointer:
 Windows Heap Manager
 Other Resources for Troubleshooting memory issue
 SafetyCheck
 Pattern Match
 /analyze Compiler Option
 Setup “GlobalFlags” or "G-Flag" and “RTC1”
 Using the memory diagnostics at runtime
 Troubleshooting additional
 Best Practices C (C Programming Best Practice)
 Memory Corruption - Common Mistakes
 Summary:
 Known Issues and Bugs:
References


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