PublicUserIdentity Was Not Correctly Loaded in Coherence Database for Reused MSISDN
Last updated on JULY 24, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version,
A MSISDN has been changed for an account and then been reused for another account.
If the poid_id0 of the new account was lower to the old one, after restart of ECE, the PublicIdentifier for this MSISDN was still linked to the old account in Coherence cache.
Steps to reproduce :
- Change the MSISDN for an account
- Reassign this released MSISDN to an another account, which the poid_id0 is lower to the first one
- Check the publicIdentifier in Coherence with CohQL:
select * from PublicUserIdentity where key()='';
For this step, the MSISDN is correctly linked to the new account.
- Restart ECE and check again the publicIdentifier in Coherence with CohQL.
The MSISDN is linked to old account.
- Make an usage Gy for the new account with this MSISDN, PublicUserIdentity is not correctly loaded in Coherence database
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