Oracle EBS R12 "OutOfMemoryError"

一般朋友遇到的,雖然沒有幫他找到具體的解決方案,給他指了一個大方向,最終他找到和合適的答案,整理如下,以備查詢

[@more@]

部分錯誤資訊:

========OC4J~oacore~default_group~1, May 29 14:28:53，OutOfMemoryError==========
JVMDUMP006I Processing Dump Event "uncaught", detail "java/lang/OutOfMemoryError" - Please Wait.
JVMDUMP007I JVM Requesting Snap Dump using '/u05/oracle/PROD/apps/tech_st/10.1.3/j2ee/home/Snap0001.20080529.142853.798822.trc'
JVMDUMP010I Snap Dump written to /u05/oracle/PROD/apps/tech_st/10.1.3/j2ee/home/Snap0001.20080529.142853.798822.trc

解決方案:

Applies to:

Oracle Applications Technology Stack - Version: 12.2
This problem can occur on any platform.
12.0.0 to 12.0.3

Symptoms

You are using e-business suite R12 and some users experience the following on screen error message:

java.lang.OutOfMemoryError

You may also see the above error in the iAS 10.1.3 log files instead of 'on screen', in such cases the on screen error may be "internal server error"

The log file message may manifest as:

JVMDUMP006I Processing Dump Event "uncaught", detail "java/lang/OutOfMemoryError"

Cause

The problem is caused by a memory issue in java code. This causes objects to not be garbage collected resulting in memory not being freed within the jvm and eventually giving java.lang.OutOfMemoryError.

This problem can result in significant performance issues when running web applications. The performance degradation is caused by MDS which is holding the page metadata reference even after the cache timeout. MDS reloads a new instance of the metadata after cache timeout without removing the old reference which was freed only on session timeout.

Solution

Apply and test 'ONE OFF TRACKING BUG FOR MDS FIX 5715952'

This patch fixes the performance issue caused by MDS which held the page metadata reference even after the cache timeout. MDS reloaded a new instance of the metadata after cache timeout without removing the old reference which was freed only on session timeout

Apply and test 'R12 ONE-OFF PATCH 6701446 HAS ISSUES'

This patch fixes the OutOfMemoryError which was caused because MDS was holding CustPath cached objects even after cache invalidation.

IMPORTANT: Do not apply these patches unless you can confirm you have a memory leak. One-off patches are not tested in the same way as standard patches, as such it is not recommended to go ahead and apply these patches until Oracle Support has verified there is a memory leak. It is important to make sure your Java Virtual machines are tuned correctly for the current load.

Presently the patches are password protected. Please contact Oracle Support for the passwords