My Oracle Support Banner

Clustered Index On POID_ID0 in Event_t table Causing Heavy Table Fragmentation (Doc ID 408175.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Microsoft Windows (32-bit)


Describe reason for event_t table fragmentation.

The POID_ID0 in event_t is getting generated randomly by the system. The associated index for poid_id0 on the event_t table (i_event__id) is CLUSTERED, which, in combination with the random poid_id0 values is causing SIGNIFICANT TABLE FRAGMENTATION.

Questions and Answers

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
Questions and Answers
 Why does the Portal installation create a clustered index against a randomly generated key value?
 What would the impact be of changing the clustered index from poid_id0 to a composite of created_t and poid_ID0?

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