My Oracle Support Banner

Not Getting Desired Caching Behavior From Dm_vertex When Changing The Caching Settings In Ctqcfg.xml (Doc ID 2257656.1)

Last updated on MARCH 16, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.16.0 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications Billing and Revenue Management(BRM), 7.5.0.16.0 version, dm_vertex,

ACTUAL BEHAVIOR  
-----------------------

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.

 
  • Start dm_vertex.
  • Execute a rate_tax_calc request(for example).
  • With different combinations of cacheControl verify mentioned cache is being loaded while vertex is started.

    • EXPECTED BEHAVIOR
    -----------------------

    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.

     

     

     

     

    Changes

     

    Cause

    To view full details, sign in with your My Oracle Support account.

    Don't have a My Oracle Support account? Click to get started!

    In this Document
    Symptoms
    Changes
    Cause
    Solution
    References


    My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.