My Oracle Support Banner

Memory Issues With Dm_oracle (Doc ID 1498947.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.5.0.0.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.

Symptoms

The dm_oracle throws PIN_ERR_NO_MEM error and the system stops working.

By sending the signal USR1 to the dm_oracle, we noticed that the free heap memory keeps decreasing, until it first crosses the high watermark (which I understand is meant as a warning when the allocated memory exceeds the 80% of the available shared memory) and then uses all of it.

This is happening especially (but not only) during billing.

The shared memory size is already 1.25GB:
- dm dm_shmsize 1342177280
- dm dm_bigsize 134217728

The bigsize could be reduced, but it seems the dm_oracle is constantly eating up shared memory, so decreasing it would not really solve the issue.

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
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.