My Oracle Support Banner

Questions Related To Errors Faced During ECE Rerating (Doc ID 1989713.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version to [Release 11.2.0]
Information in this document applies to any platform.


The purpose of this article is to answer some questions regarding common errors faced while testing rerating feature in ECE.

Questions and Answers

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
Questions and Answers
 1. While starting to test rerating using pin_rerate command,  there is an error "op_rate_and_discount_event error" in cm pinlog. What is the reason ?
 2. User ran the rerating command "pin_rerate -a 2559383 -t 01/09/2015". From cm pinlog one can see that rerate request has been sent to ECE for rerating but emgateway logs an error "The supplied request payload does not conform to the service spec" and that causes usage request not to be built fully and rerating failed in ECE as well as BRM. What is the remedy for this ?
 3. After making necessary changes (as per previous answer), executed "pin_rerate -a 6695067 -t 02/06/2015". But the rerate job is inserted in job_rerate_t with a status of -1 where as it should have 1. Why ?
 4. After enabling ECERating parameter, executed "pin_rerate -a 6695067 -t 02/06/2015", rerate job created with status 1. Following this, executed "pin_rerate -process jobs", then, rerate job got updated to status 2 as expected, but getting error in CustomerUpdater log "Rated event cache flush check failed". Why ?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.