(Doc ID 858390.1)

Last updated on JUNE 22, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.
***Checked for relevance on 15-Aug-2011***
***Checked for relevance on 10-Jun-2014***


-- Problem Statement:

When pipeline was not processing anything, run dup_check_limit (which is a slightly modified version of OOB application set_dup_check_limit.pl) on May 19th 2009 to set the BufferLimit to 20090419 and StoreLimit to 20090320. An error message ERR_MEM_MON_PROCESS_LIMIT  logged on the monitor and the three out of the four pipelines were stopped. Only ALL_RATE pipeline was  still running (PARSING, PRE_PROCESS, PRE_RECYCLE were stopped). The command  dup_check_limit was run every day and the BufferLimit and StoreLimit were moved by one day every day.

 For example, if today is May 20th 2009, the BufferLimit will be set to 20090420; StoreLimit will be set to

MemoryMonitor was set as below:

   ScaleUnit = P
   WarningFreeMemLimit = 10
   ShutdownFreeMemLimit = 5

The error shown on the monitor is as below:

/portal/7.2.1/ifw/bin/ifw: An error occurred during processing.

Originator : ifw.MemoryMonitor
Destination :
Arguments : SHUTTING DOWN:

State : false
Severity : CRITICAL
Thread : 1

Portal Pipeline Server / Version 7.2.1 10088 finished at 19.05.2009 12:51:46.

In another day, the following message is logged:

It seems the pipeline always shuts down at this memory limit (about 16GB).

What could be the cause of this problem?  Is there a way to raise the limit?


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms