Check existence of required tables and indexes

It is a requirement that your environment conforms with the default database schema that will be deployed when creating the schema for Product Master. This ensures for the majority of installations optimal performance.

Symptoms

If you are having problems with missing or corrupted indexes, you should check the existence of required tables and indexes.

Environment

$JAVA_RT com.ibm.ccd.common.util.SystemDB

|Extra Indexes
|=========================================================================|
|  There are no extra indexes
|_________________________________________________________________________|
_________________________________________________________________________
|Changed Indexes
|=========================================================================|
|  There are no changed indexes
|_________________________________________________________________________|
_________________________________________________________________________
|Missing Indexes
|=========================================================================|
|  CTG_1_UK
|  DOA_0_UK
|  ISEC_OAC_0
|  ISEC_OBT_0

Diagnosing the problem

If your database administrators suggest modifications to the current schema (for example, deleting, adding or modifying indexes), it is recommended to recheck those changes with product support so potential negative side effects can be avoided. This also will ensure that schema changes, which will improve performance for all customers will be part of the default schema in the future. To check, issue the following command: $JAVA_RT com.ibm.ccd.common.util.SystemDB

Resolving the problem

If you need to check existing index definitions, one option would be to query Database system tables. This would be only necessary if you find some index definition deviations with SystemDB utility and would need to compare with the required original definitions. The schema definition can be found in the $TOP/src/db/schema/gen/* directory.