beGroveller Does Not Remove Expired Buckets (Doc ID 2188140.1)

Last updated on OCTOBER 05, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.1 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications Network Charging and Control (OCNCC) release version 4.4.1, when wallet's Expiry Dates are too old (more than 30 days in the past), they are not processed by the beGroveller any more. 

beGroveller process is responsible for searching the database for unused wallets, and sending them to the correct beVWARS process when requested.
During normal processing, events are triggered only when a subscriber interacts with the wallet. Some events (such as expiry and periodic charges) should be triggered regardless of whether the wallet has been used by a subscriber recently or not.
In order to process these events, beGroveller collects and sends lists of wallets IDs to beVWARS for processing. This processing triggers any events which are due to occur in the same way a normal interaction would, except wallets triggered from beGroveller lists do not trigger any message handlers.

Changes

 

Cause

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