Discrepancies in the dbchck Log

After completion of the dbchck.exe script, the dbchck.log file generated might contain discrepancies noted as failures.

Some errors noted in the dbchck.log file are not acceptable and must be addressed. An example of such an error follows:

Dictionary column FIN_PERIOD_ID not in physical schema! Dictionary different from physical schema for column dictionary: REVISED_COST numeric(22,7) null physical: REVISED_COST decimal(10,0) null

This error is caused by a mismatch in the data type definition of the column in the logical and physical schema. The definition of a column in the logical and physical schema must be synchronized; you can synchronize the logical definition with the physical schema using Siebel Tools. After the synchronization is done, run dbchck.exe again.

Note: LONG columns, defined as LONG VARCHAR columns in the Siebel Repository, are physically created as VARCHAR columns by DB2 for z/OS. The dbchck utility does not generate errors for LONG columns in these circumstances; this is expected behavior on the DB2 for z/OS platform. For additional information, see About Long Columns and Siebel Utilities.

For more information about using the dbchck utility, see the section Checking the Repository in the Siebel Enterprise Installation Manager Administration Guide.