About Moving the Customized Repository and Schema Definition Files

Upgrades: All upgrades.

Environments: Production test and Production environments

This topic is part of an upgrade process. See Performing a Siebel Database Upgrade.

When you upgraded your development environment, the new customized repository was exported to a file called custrep.dat and the modified schema definition was exported to a file called schema.ddl in the SIEBEL_ROOT\dbsrvr\db2390\ directory (Windows) or the $SIEBEL_ROOT/dbsrvr/db2390/ (UNIX) directory on the Siebel Server client computer from which you ran the upgrade. These files are used as the schema input on the production upgrade.

If the development and production upgrades are run on different midtier computers, then you must copy the schema.ddl and custrep.dat files to the production midtier computer before running the production upgrade.

If you modify repository objects or schema definitions after completing the development upgrade (upgphys), you must regenerate the schema.ddl and custrep.dat files. See Regenerating the Siebel Repository Definition Files for further information. You must then copy the files from the development to the production midtier computer again.

In the production environment, the custrep.dat file is used by the Siebel Upgrade Wizard to import the New Customer Repository and theschema.ddl file is used by the Siebel Upgrade Wizard to create the new database schema.