GET_ECE_BALANCES Failed for Some Accounts After RollingUpgradeServer Failed
(Doc ID 2551493.1)
Last updated on SEPTEMBER 17, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Oracle Communications Elastic Charging Engine(ECE), 22.214.171.124.0 Version,
After a failed rollingUpgrade, when executing the PCM_OP_BAL_GET_ECE_BALANCES opcode, the following message returned: PIN_ERR_NO_CREDIT_BALANCE
After executed a synchronization on accounts from BRM to ECE, then the balances cache is updated and the opcode works fine.
It is found that PublicUserIdentity does not exist any key entry for the telephone number, so the ECE_GET_BALANCES failed. After the synchronization, a new entry is added back inside PublicUserIdentity cache, and then ECE_GET_BALANCES works fine.
Is it possible that when rollingUpgrade server fails causing this cache to miss some entries?
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