My Oracle Support Banner

BI Publisher 11g - Oracle Process Manager Notification Process Cannot Allocate Memory And Process Ping Failed Messages (Doc ID 1390240.1)

Last updated on NOVEMBER 11, 2023

Applies to:

BI Publisher (formerly XML Publisher) - Version 11.1.1.5.0 to 11.1.1.5.0 [Release 11.1]
Information in this document applies to any platform.

Symptoms

A BI Publisher 11g architecture is suffering an OPMN performance issue.

This issue also shows up when running the  XML returned by opmn metric op=query

Over a period of days, the memory consumed by the OPMN process steadily increases. Eventually an operating system memory threshold is reached which causes the system and applications to hang and/or throw memory related errors.

Here is an example of the several Ping failed messages which are populating the opmn.log files.

[TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed

Steps to reproduce
-------------------
1) Configure 11.1.1.5 instance.
2) Start instance with OPMN.
3) Monitor OPMN process over time for memory leak.

Workaround
------------
Restart the OPMN frequently.

Changes

No changes were made to the environment.

Cause

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
Symptoms
Changes
Cause
Solution
References


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