Objects With CacheResidency 'DBONLY' Read Into Pipeline Memory Cache
Last updated on SEPTEMBER 25, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Pipeline Manager
Accounts are getting rated in pipeline even though PIN_FLD_OBJECT_CACHE_TYPE set to DBONLY.
The CDR is getting rated successfully.
The CDR passed for account should be rejected as PIN_FLD_OBJECT_CACHE_TYPE is set DBONLY
The issue can be reproduced at will with the following steps:
1. A new business profile was created with CacheResidency Value : DBONLY by modifying the pin_business_profile.xml
2. Cache Residency distinction was enabled in bus_params_billing.xml [ <CacheResidencyDistinction>enabled</CacheResidencyDistinction>]
3. Restart the BRM and create an gsm account.
4. The account for which the default PIN_FLD_OBJECT_CACHE_TYPE was 2 (BATCH) was updated to 3 (DBONLY) by associating the above business profile to the account using the opcode PCM_OP_CUST_CHANGE_BUSINESS_PROFILE
5. Restart the pipeline and pass cdr
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