Upgrade Guide for DB2 UDB for z/OS and OS/390 > Performing the Siebel Tools Repository Merge >

Safeguarding the New Custom Repository Export File

Upgrades: All upgrades.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform the Upgrade.

The Siebel Software Configuration utility exports two customized repository files called custrep.dat and schema.ddl, located in the DBSRVR_PLTFRM_ROOT directory on the Siebel Server from which you ran the upgrade. Locate these files and make a backup copy of them.

If you make any changes to your custom repository after running the development upgrade Siebel Software Configuration utility, including reapplying custom extensions or modifying EIM mappings in the two previous steps, you must export a new copy of the repository before performing the production upgrade.

Use the script master_exprep.ucf, located in DBSRVR_ROOT, to export your current repository to the file that you designated as the output file in the Siebel Software Configuration utility. You can use the Siebel Software Configuration utility to invoke the master_exprep.ucf script that exports your current repository. Before you export the repository, you should make sure that all Siebel Tools projects are unlocked to promote a stable environment.

The master_exprep.ucf script calls the repimexp utility, which connects to two separate repositories—the repository whose structure is to be extracted, and the repository whose content is to be extracted. Apart from unusual circumstances, you always extract both the structure and content of the same repository.

For information on exporting repositories, see Configuring Siebel eBusiness Applications.