Balance Group Of Accounts with Cache Residency Distinction Set to DBONLY Get Loaded Into Pipeline Memory
Last updated on JULY 14, 2015
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Configure the validation templates and profiles for DBONLY cache residence distinction (PIN_FLD_OBJECT_CACHE_TYPE = 3) by following all the steps in BRM documentation, Setting Up Business Profiles and Validation Templates. After that, check account/service data (as example below) is not loaded in pipeline memory, but balance_group associated with those accounts are loaded in pipeline memory. Why do DBONLY objects get loaded into pipeline memory?
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