Performing a Siebel Repository Merge

Environments: Development environment only.

Platforms: Windows, UNIX, IBM z/OS.

This task merges customizations in the Prior Customer Repository (your current repository) into the New Customer Repository (the repository in the new Siebel release).

The repository merge typically takes five to seven hours to complete.

Requirement: The workstation on which the merge will occur must have a minimum of 512 MB of RAM and at least 2 GB of virtual memory or a 2–GB page file. Inadequate system resources is one of the most common causes of repository merge failures. If your repository includes a large amount of customization, then additional memory might be required.

Note: Before running a repository merge, verify that EnableSafeboot=true is present in the [InfraObjMgr] section of the tools.cfg file.

To merge the repository

  1. Verify that all Siebel Tools projects are checked in and unlocked.

  2. Close network connections to all repository users and exit Siebel Tools.

  3. Open the tools.cfg file in the new Siebel release. It is located in the following directory:

    $SIEBEL_HOME\bin\lang_code 

    In this path, lang_code is the language, for example enu.

  4. Locate the SIEBEL section, and verify that the parameters are set as shown in the following example.

    Parameter

    Value

    EnableToolsConstrain

    FALSE

    SymStrPrefix

    X_
  5. Save the file and close it.

  6. Navigate to Control Panel, System, Advanced, Performance Settings, and then Visual Effects.

  7. Click Adjust for best performance.

  8. Start Siebel Tools in the new Siebel release, using the following command:

    $SIEBEL_HOME\bin\siebdev
    Note: The merge0.txt file will be generated in the $SIEBEL_HOME\bin directory.
  9. From the Tools menu, choose View, Options, and then Language Settings.

  10. Verify that the language mode setting is set as desired.

    This will be the user interface language for Siebel Runtime Repositories based on the New Customer Repository. It will also be the language used by the postmerge utilities.

  11. From the File menu choose the Open Repository command to open the Prior Customer Repository.

  12. From the Tools menu, choose Upgrade, then the Upgrade Application menu item.

    The Merge Repositories dialog box appears.

    In the Merge Repositories dialog box, there is an arrow going from Prior Standard Repository to New Standard Repository and then on to New Customized Repository. There is another arrow going from Prior Standard Repository to Prior Customized Repository and then on to New Customized Repository.

    The Merge Repositories dialog box provides four options:

    • Merge. This button merges the repositories you specify to produce a New Customer Repository.

    • Cancel. This button cancels the repository merge and exits the Merge Repositories dialog box.

    • Advanced. This button opens the Merge Options dialog box.

  13. In the Merge Repositories dialog box, choose the repositories listed in the following table.

    Drop–Down List Item

    Value to Choose

    Prior Standard Repository

    Prior x.x Siebel Repository, as appropriate for the version from which you are upgrading

    Prior Customized Repository

    Prior Customer Repository

    New Standard Repository

    New Siebel Repository

    New Customized Repository

    New Customer Repository

  14. Click Advanced.

    The Merge Options dialog box appears.

  15. In the Merge Options dialog box, click the check boxes to activate or deactivate the merge options:

    • Abort merge if more than x errors occur. Activate this option to abort the repository merge automatically if more than a designated number of errors occur.

      Caution: The typical Repository merge generates many benign errors. If you select this option, then set the number of errors to a large value. This will help prevent the Repository merge from aborting due to benign errors.
    • Incorporate Custom Layout. Activate this option to help preserve field and button placement on prior custom or modified forms, views, and screens. Select a prior release and style for label placement.

      After you have made your selections, click OK.

      The Upgrade Check List dialog box appears.

  16. In the Upgrade Check List dialog box, verify that each requirement has been met. When they have been met, select all the check boxes and click Continue.

    Caution: The upgrade might fail if all the items in the checklist are not completed.

    After the merge completes, a dialog box appears, requesting that you make a backup of the New Customer Repository.

Related Topics

About the Siebel Repository Merge