Last updated on JULY 20, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management(BRM), 220.127.116.11.0 version, dm_vertex,
The user is not getting the desired caching behavior from dm_vertex when changing the cache control settings in 'ctqcfg.xml' file as mentioned below.
When there is no cache block in 'ctqcfg.xml', all the queries are executed every time. When the cache setting is to enable both Loc and Rte (as dynamic or preload), it queries LocGeo and RteCde every time. Any other table should not be queried. Here for “Preload” the user is expecting to see a couple of large queries when dm_vertex starts, caching the data, and expect no more DB queries from then on. dm_vertex would then use cached data.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms