Upgrade Guide for Microsoft Windows > Postupgrade Tasks > Postupgrade Tasks for All Environments >

Safeguarding the New Custom Repository Export File

CAUTION:  This procedure only applies to development environment upgrades. For production environment upgrades, skip this procedure and proceed to Producing a New Custom Configuration File.

The Siebel Software Configuration Utility exports the new customized repository to a file called custrep.dat, located in the DBSRVR_PLTFRM_ROOT directory on the Siebel Server from which you ran the upgrade. Locate this file and make a backup copy of it. You need this file for the upgrade of the production database.

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 DBSRVR_PLTFRM_ROOT/master_exprep.ucf 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.

The master_exprep.ucf 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 the "Repository Management Tools" chapter of Siebel Tools Reference.

NOTE:  Before you export the repository, you should make sure that all Siebel Tools projects are unlocked to promote a stable environment.


 Upgrade Guide for Microsoft Windows
 Published: 20 October 2003