DM_ORACLE Goes Down While Running PIN_LEDGER_REPORT
(Doc ID 973569.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.1 [Release 7.3.0]
Information in this document applies to any platform.
Below command was executed to run the GL report, from BRM_home/apps/pin_billd :
Within few minutes , DM_ORACLE process would go down .
Dm_oracle.log shows below error :
Dm_oracle.pinlog shows below error :
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?
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