My Oracle Support Banner

Pin_bill_accts Failing with DM NO_MEM Error on STEP_NEXT After Some Batches Completed (Doc ID 2204946.1)

Last updated on AUGUST 16, 2018

Applies to:

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


On : version, DM

Performing testing between PS14 and PS16+ Patch 24588097, pin_bill_accts queries are now getting NUM_SUPPRESSED_CYCLES for each /billinfo in addition to POID and ACCOUNT_OBJ.


Process pin_bill_accts for pay type in following order:

Paytype Run Result # of accounts
10007 1 Success 325795
Sponsorship 1 Success 2806
10000 1 Success 239
10021 1 Failed 2640000
2 Success 1581381
10001 1 Success 466121
10003 1 Failed 330000

The account to be processed should be about 1113154 for paytype 10003.

Same runs on the PS14 environment succeeded with these volumes. It appearred that dm_oracle fetches were leaking memory.
The addition of the extra field in the search output should not have this significant impact on dm shared memory sizing given in the pin_bill_accts settings.




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.