Siebel Database Upgrade Guide for DB2 UDB for z/OS > Performing the Siebel Repository Merge >

Regenerating the Siebel Repository Definition Files

Upgrades: All upgrades.

Environments: Development environment only.

Platforms: All platforms.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

If you have modified repository objects after the development environment upgrade (upgphys) and before upgrading the production test environment, you must regenerate the schema.ddl and custrep.dat files. These files were created during the upgphys:

• Schema.ddl. This file contains the logical definition of the Siebel database.
• Custrep.dat. This file contains the definition of repository objects.

These files are used as input to the production test and production environment upgrades. If you modify the object definitions or the schema definitions in the repository after these files have been created, you must regenerate the files.

Regenerating the schema.ddl File

Use this procedure to regenerate the schema.ddl file.

To regenerate the schema.ddl file

1. On the Siebel Server where the Siebel Database Server files are installed, navigate to the following location:

   Windows: SIEBEL_ROOT\bin

   UNIX: $SIEBEL ROOT/bin

2. Run the following command:

   ddldict /u DatabaseOwner /p Password /c "ODBCDataSource" /d TableOwner /f DBSRVR_ROOT\DatabasePlatform\schema.ddl /e y /a y /l SiebelLogDir\sch_dict.log /n "Siebel Repository" /t dcir

   where:

   • DatabaseOwner is the Siebel database Administrator account name.
   • Password is the Siebel database Administrator account password.
   • ODBCDataSource is the ODBC name for connecting to the database. Enclose the name in quotes.
   • TableOwner is the Siebel table owner name.
   • DBSRVR_ROOT is the absolute path to the Siebel Database Configuration Utilities installation directory.
   • DatabasePlatform is the Siebel Database Configuration Utilities directory name for the database, that is, DB2390. The example shows Windows path syntax. On UNIX systems, use UNIX path syntax.
   • SiebelLogdir is the path to the directory where you want the output log placed (log output directory). The example shows Windows path syntax. On UNIX systems, use UNIX path syntax.
3. After the command completes, review the output logs for errors. If the log indicates there are errors, create a service request (SR) on My Oracle Support.

Regenerating the custrep.dat File

Use this procedure to regenerate the custrep.dat file.

To regenerate the custrep.dat file

1. On the Siebel Server where the Siebel Database Configuration Utilities files are installed, navigate to the following location:

   Windows: SIEBEL_ROOT\bin

   UNIX: $SIEBEL ROOT/bin

2. Run the following command:

   repimexp /a e /u DatabaseOwner /p Password /c "ODBCDataSource" /d TableOwner
/r "New Customer Repository" /f DBSRVR_ROOT\DatabasePlatform\custrep.dat
/l SiebelLogDir\exprep.log

   where:

   • DatabaseOwner is the Siebel database Administrator account name.
   • Password is the Siebel database Administrator account password.
   • ODBCDataSource is the ODBC name for connecting to the database. Enclose the name in quotes.
   • TableOwner is the Siebel table owner name.
   • DBSRVR_ROOT is the absolute path to the Siebel Database Configuration Utilities installation directory. The example shows Windows path syntax. On UNIX systems, use UNIX path syntax.
   • DatabasePlatform is the Siebel Database Configuration Utilities directory name for the database, that is, DB2390.
   • SiebelLogdir is the path to the directory where you want the output log placed (log output directory). The example shows Windows path syntax. On UNIX systems, use UNIX path syntax.
3. After the command completes, review the output logs for errors. If the log indicates there are errors, create a service request (SR) on My Oracle Support.