My Oracle Support Banner

Question Regarding Cm_cache_update_entry() (Doc ID 1531289.1)

Last updated on AUGUST 10, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Information in this document applies to any platform.

Goal

One is using cm_cache in some custom code. In detail, one is creating a flist to capturing some CM specific information and store this information in a global cm_cache. Whenever needed, one can run some opcode to pull out that CM specific information for debugging purpose.

The logic is like below :

- Gather cm specific information and use to create cm_flistp;
- set key = current cm pid;
- cm_cache_update_entry (config_XXXX_cm_context_flist_ptr, (void *)&key, cm_flistp, &err);

But there is no enough information regarding how cm_cache_update_entry manages memory. The question here is, after calling cm_cache_update_entry(), is there a need to destroy cm_flistp ? In other words, does cm_cache_update_entry() make a copy of input cm_flistp or use the existing cm_flistp memory?
 

Solution

To view full details, 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 a vibrant support community of peers and Oracle experts.