Explanation About CM Configuration Parameter "cache_beid" (Doc ID 1178253.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 to 7.5.0.0.0 [Release 7.3.0 to 7.5.0]
Information in this document applies to any platform.
***Checked for relevance on 12-Jun-2012***
***Checked for relevance on 03-06-2014***

Goal

Scenario:

*  There is a problem starting cm process after enhancement of product catalogue, like configuration of resources (beid).
*  Current total number of resources is about 29000.
*  In case original parameters are used, CM does not start:

- cm_cache fm_price_cache_beid 26000, 16777216, 32
- cm cm_cache_space 536870912

*  After changing the parameters to following numbers:

- cm_cache fm_price_cache_beid 40000, 20777216, 32
- cm cm_cache_space 536870912

*  CM starts, but again cannot start CM in loglevel 3 (CM does not start or it takes more than 2 hours to start).
*  In documentation there seems to be no guidelines for correct configuration of this value and possible impact of not complete / wrong configuration / impact of increasing these parameters on hardware resources.

Solution

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