My Oracle Support Banner

E1: UBE: Case Study on "MEMORY ALLOCATION FAILURE" Errors on EnterpriseOne Batch Applications (Doc ID 1272974.1)

Last updated on MAY 30, 2017

Applies to:

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

Purpose

Information Center: Overview of Universal Batch Engine in the JD Edwards EnterpriseOne Tools and Technology Product > Information Center: Troubleshooting Universal Batch Engine in the JD Edwards EnterpriseOne Tools and Technology Product > Note 1513116.2

 

This document provides an analysis of common common causes of Memory Allocation errors in batch applications.

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
 Overview
 Example 1: CMRB000007 - ERROR: Memory allocation failed
 Example 2: CAC0000018 - Failed to allocate memory for stored key
 Example 3: Not enough storage is available to process this command
 Example 4: SQL0000047 - Allocation failed
 Example 5: OCI0000020 - Out of memory for allocating return values
 Analysis
 Common Questions on Insufficient Memory Issues
 Q1. What are commonly reported UBEs that may produce the MEMORY ALLOCATION FAILURE issue?
 Q2. What is maximum size of memory can be allocated per process/kernel?
 Q3. How Does EnterpriseOne manage Memory?
 Q4. How to estimate the memory size needed?
 Q5. What is the best way to work around this type of error?
 Q6. Are there some example of changing physical memory size?
 Q7. Is there way not to dump memory diagnostic in dmp file when jdemem code log Memory Allocation Failure?
References


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