My Oracle Support Banner

Table Index CMN_PERSISTENT_STORE_IDX_KEY Becomes Fragmented and Uses More Space (Doc ID 1325149.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.
Checked for relevance on 12-03-2013

Symptoms

The cmn_persistent_store_ix_key index uses more extents than usual.

Specialized tools like nagios or any other monitoring tool can be used as front-end to warn the System Administrator that the index on that table has grown and crossed a pre-defined limit.

Index fragmentation can have an impact on performance as they are queried to quickly retrieve data from the tables. It is important to detect, then solve index fragmentation when it happens in order to maintain optimal performance.


From the Oracle Database itself, use the following queries to learn about that index and related table usage:

Changes

  1.    The CMN_PERSISTENT_STORE table has seen a large number of inserts and deletions over time

  2.    The CMN_PERSISTENT_STORE total row count (or size) has increased

  3.    The eserv.config pstore section has changed

  4.    The oraPStoreCleaner startup script has changed

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
    The CMN_PERSISTENT_STORE table has seen a large number of inserts and deletions over time
    The CMN_PERSISTENT_STORE total row count (or size) has increased
    The eserv.config pstore section has changed
    The oraPStoreCleaner startup script has changed
Cause
 Theoretical background
    xmsTrigger, xmsAgent, xmsStore VS cmn_persistent_store, cmn_persistent_store_idx_key
 Cause determination
    The CMN_PERSISTENT_STORE table has seen a large number of inserts and deletions with no maintenance
    The traffic increased, the table contents grow
    The pstore section configuration changed
    The oraPStoreCleaner configuration changed
 Cause justification
    The index needs some maintenance
    The traffic increased, the table contents grow
    The pstore section configuration changed
    The oraPStoreCleaner configuration changed
Solution
    Solution when the table has seen a large number of inserts and deletions
    Solution when the traffic increased, the table content grows
    Solution when the the pstore section configuration changed
    Solution when the oraPStoreCleaner configuration changed
References


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