beGroverlling Misses Buckets Created with a Recent Expiry Date (Doc ID 2822098.1)

Last updated on MARCH 27, 2023

Applies to:

Symptoms

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).

Cause

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