Implementing Siebel Business Applications on DB2 UDB for z/OS > Importing the Siebel Repository and Performing Postinstallation Tasks >

Validating the Siebel Schema

This task is a step in the Process of Completing the Siebel Database Implementation.

After you install the Siebel Database and import the repository, you must compare the physical database schema with the repository to make sure that there are no inconsistencies between them. Use the Siebel Server utility, dbchck.exe (Windows) or dbchck (UNIX), located in the bin subdirectory of your Siebel Server installation directory, to make this comparison.

You can use the dbchck utility to validate data relationships, including foreign keys and the list of values. You can also use this utility when you have made changes to the extensibility of your Siebel database.

The most popular mode in which to run dbchck is using the option /dict /all. This option provides a comprehensive log file that lists all of the discrepancies between the logical data model defined in the repository you specify and the physical database schema in the Siebel database you run the utility against.

To validate the Siebel Schema

1. From the SIEBSRVR_ROOT\bin directory (Windows) or the SIEBSRVR_ROOT/bin directory (UNIX), locate dbchck.exe (Windows) or dbchck (UNIX).
2. (Windows only) Delete the dictionary cache file (diccache.dat) before running dbchck, and verify that there are no EIM or Siebel Remote operations running.

   The dbchck utility creates a new diccache.dat file before carrying out the integrity check. By deleting the existing diccache.dat file before starting dbchck, you ensure that dbchck validates against the Siebel Repository you specify.

   NOTE:  If you stop any EIM or Siebel Remote processes, you can restart them after dbchck has run.

3. Source environment variables as appropriate for your platform, using either siebenv.bat (Windows) or siebenv.sh or siebenv.csh (for UNIX).

   Environment variable scripts are located in the SIEBSRVR_ROOT\bin directory (Windows) or the SIEBSRVR_ROOT/bin directory (UNIX).

4. Source the database profile.
5. Run dbchck using the following syntax:

   dbchck /u SADMIN /p password /t SIEBTO /r "Your Siebel Repository Name" /l dbchck.log /dict /all /s ODBC data source

   where:

   • password = login password to the database.
   • Your Siebel Repository Name = the repository you want to compare against the physical data model; in the installation, the default value is "Siebel Repository".

     NOTE:  You must specify your repository name within quotation marks ("") after the repository name parameter (/r).

   • ODBC data source = the ODBC data source applicable to the repository.
   • SIEBTO = the Siebel Schema Qualifier.

     NOTE:  To view all the dbchck parameters with their descriptions, use option /h.

     Any discrepancies found appear on the screen. Detailed information is written to a log file in the SIEBSRVR_ROOT\bin directory (Windows) or the SIEBSRVR_ROOT/ bin directory (UNIX).

     NOTE:  The log file name is the name you specified after the log file parameter (/l). In the previous example, the file is named dbchck.log.

6. Review the log file generated as a result of running this script. Any discrepancies are flagged as failures. Investigate all discrepancies.

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.

For more information about using the dbchck utility, see the following documents:

• 475677.1 (Doc ID) on OracleMetaLink 3. This document was formerly published as Siebel FAQ 1128.
• 477235.1 (Doc ID) on OracleMetaLink 3. This document was formerly published as Siebel Troubleshooting Steps 20.