Creating database indexes to improve performance

Enabling some IBM Content Navigator features creates add-on database tables and columns that are not automatically indexed. After you create indexes, queries on those properties run faster and return results faster than queries on tables or columns that are not indexed.

About this task

For example, when you connect to a repository from the IBM Content Navigator administration tool, you must enable the teamspaces feature on the repository. Enabling the teamspaces creates an add-on in the object store and also creates the *_clbTeamspacestate property. However, the *_clbTeamspacestate property is not automatically indexed, so queries for that property run slower than queries on other columns that are indexed. Therefore, to improve performance, you should create database indexes.

Procedure

To create database indexes:

  1. For a large IBM FileNet® P8 repository with many teamspaces, such as more than 1000, that are slow or time out too quickly, create a database index on the table named Container.
    The index for the table Container contains four columns: object_class_id, u6a16_clbteamspacestate, u47d8_clbteamspacename, and object_id.
    1. If you also have many roles that are associated with a teamspace, increase object security cache entries and security descriptor cache entries appropriately in Content Platform Engine from the default value of 8192.
  2. To browse the folder tree in an IBM FileNet P8 repository:
    1. Create an index on the database table named Relationship.
      The index for the database table Relationship contains two columns: tail_id and head_id.
  3. For an IBM FileNet P8 repository, that is slow or times out too quickly when opening the all searches view, create a database index on the table named Docversion.
    The index is for the database table Docversion on the *_Searchtype column.
  4. For an IBM FileNet P8 repository, that is slow when listing items from a MyCheckOutList list, create a database composite index on the table named Docversion.
    The composite index is for the database table Docversion on the MODIFY_USER and IS_RESERVE columns.
  5. For an IBM FileNet P8 repository that is slow when opening the Entry Templates View, create a database index on the table named Docversion.
    The index is for the database table Docversion on the MIME_TYPE column
  6. For an IBM FileNet P8 repository that is slow when searching for tags, create a database composite index on the table named UT_CLBTAG.
    The composite index is for the database table UT_CLBTAG on the *_CLBTAGVALUE and *_CLBSUMMARYDATA column.
  7. For IBM FileNet P8 that is slow when creating a new document or configuring new default templates, you can use a database administration tool to create a database index on the table named Docversion. The index is for the database table Docversion on the *_ClbIBMDocsState column. Or, you can use the administration console to create a database index for the ClbIBMDocsState property.