Lifecycle Expiration Time Is Not Reflecting as Expected in Customer Cache
(Doc ID 2962259.1)
Last updated on JULY 20, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.5.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
-----------------------
LifeCycle Expiration Time is not reflecting as expected in Customer Cache.
EXPECTED BEHAVIOR
-----------------------
Lifecycle Expiration Time should be reflected correctly in Customer Cache, to match with what is printed in emGateway1.log.
STEPS
-----------------------
Create a customer account
Check in customer cache
See that "Life cycle Expiration time = 0"
Check in EMGateway log
See that "<ExpirationTime>Sun Aug 13 23:59:59 AST 2023</ExpirationTime>"
Cause
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
Symptoms |
Cause |
Solution |
References |