My Oracle Support Banner

DM_ORACLE Goes Down While Running PIN_LEDGER_REPORT (Doc ID 973569.1)

Last updated on JANUARY 18, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 to 7.3.0.0.1 [Release 7.3.0]
Information in this document applies to any platform.

Goal

Below command was executed to run the GL report, from BRM_home/apps/pin_billd :

pin_ledger_report -mode run_report -start 09/01/09 -end 10/01/09 -type billed_earned -report gl_report_b-e-d -detail -posted


Within few minutes , DM_ORACLE process would go down .
Dm_oracle.log shows below error :

<dm_malloc(22712):WARNING ->heap size(98279) CROSSED high water mark(78623)>


Dm_oracle.pinlog shows below error :

<pini_flist_heap_grow (first extension) returned an error. size=1024, pin_err=1(PIN_ERR_NO_MEM)>



Below steps were taken to avoid this memory issue :
1. Adjusted the shm_size and shm_bigsize parameters of the dm_oracle , so that maximum heap memory is available for dm_oracle while processing the data. But it did not help.
2. Latest fixes in dm_oracle addressing some memory leak issues were applied , but it did not help. The patch was 8293177 .
3. transaction_grouping parameter was enabled and used in the pin_billd/pin.conf file, but it did not help.


Also , note that if one tries to increase the shared memory in dm_oracle to more than 1GB , the dm_oracle process will not start. This is because of the limitation on HP-UX platform where , a max of 1GB of memory only can be allotted to a process.

How can we avoid the memory issue when we run pin_ledger_report?

Solution

To view full details, 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 a vibrant support community of peers and Oracle experts.