Avoiding Excessive Table Fragmentation

Before running Siebel EIM, consult an experienced DBA in order to evaluate the amount of space necessary to store the data to be inserted in the EIM tables and the Siebel base tables. Also, for example with Oracle Database, you can make sure that the extent sizes of those tables and indexes are defined accordingly.

Avoiding excessive extensions and keeping a small number of extents for tables and indexes is important because extent allocation and deallocation activities (such as truncate or drop commands) can be demanding on CPU resources.

To check whether segment extension is occurring in Oracle Database

• Use the SQL statement that follows to identify objects with greater than 10 extents.

  Note: Ten extents is not a target number for segment extensions.

  SELECT segment_name,segment_type,tablespace_name,extents
  FROM dba_segments
  WHERE owner = (Siebel table_owner) 
  and extents > 10;
  

  To reduce fragmentation, the objects can be rebuilt with appropriate storage parameters. Always be careful when rebuilding objects because of issues such as defaults or triggers on the objects.