beGroverlling Misses Buckets Created with a Recent Expiry Date
(Doc ID 2822098.1)
Last updated on NOVEMBER 16, 2021
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC), there is a race condition that can occur if a new bucket is created or an existing bucket is updated with an expiry date set to anything from the current time up to a couple of seconds in the future.
This race condition prevents the bucket from ever expiring "automatically", ie. found by the beGroveller and sent to the beVWARS for processing.
Manually triggering the Wallet will trigger the bucket to immediately expire as expected (provided the expiry date is in the past).
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