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 APRIL 03, 2019
JD Edwards EnterpriseOne Tools - Version 8.98 and later Information in this document applies to any platform.
Note: If you encounter business function error while using a standard application or standard report (UBE), the issue maybe already reported. You can install the available ESU to fix the issue. If issue has not yet been reported, open a service request with the team that support the standard application or UBE. Example, select product JD Edwards EnterpriseOne Sales Order Management while opening a SR if you are encountering business function issue while using P4210. If you encounter issue with a standard business function which is being used in your custom object (application or UBE), first check if the issue also occur with the standard application or UBE. If issue does not occur, then most likely this is not a 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 an EnterpriseOne 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. The information in this document maybe helpful for developing custom business function.
This document contains examples of some memory issues. It is not meant to be all encompassing.
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.
Please also refer to the second part document in this knowledge 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 is intended for the EnterpriseOne developer and requires an advanced knowledge of the EnterpriseOne Development Tools and Visual C programming.
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 "Support Policies" in Document 166650.1 Working Effectively With Oracle Support - Best Practices. For custom business function, field services may need to be engaged.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!