BE.beVWARSExpiry.expireBucketsForExpiredWallets Does Not Affect Operator Update Wallet Terminations
Last updated on JULY 01, 2013
Applies to:Oracle Communications Network Charging and Control - Version 2.2.0 and later
Oracle Solaris on SPARC (64-bit)
In all versions of NCC (Network Charging and Control), when a Wallet is manually moved to Terminated via an Operator Update in the SMS (Service Management System) Screens, the Wallet is correctly terminated but the Buckets remain with unaltered expiry dates.
This behaviour is unaffected by the eserv.config parameter BE.beVWARSExpiry.expireBucketsForExpiredWallets, which as per the Technical Guide:
Syntax: expireBucketsForExpiredWallets = true|false
Description: Controls whether wallet expiry triggers bucket expiry. If true, any buckets under the wallet will be expired when the wallet expires.
Optionality: Optional (default used if not set).
true - All buckets with a positive or zero value in a wallet will be expired when the wallet is expired, even if the buckets are not due to expire yet.
false - Buckets are expired when their own expiry date passes. Note: This means the wallet will not be deleted from the system, but will instead be set to Removed state and kept until the last bucket is expired.
Notes: If expireNegativeBuckets is set to false, buckets with a negative value will not be deleted, regardless of the value of this parameter. Using this parameter will remove any positive value the wallet holds when the wallet expires.
Example: expireBucketsForExpiredWallets = false
Manual Operator Update termination of Wallet.
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