Optimizing Performance of the Repository Merge

There are several ways in which you can reduce the time required to complete the repository merge.

• Optimize the computer on which you are running the repository merge as follows:

  • Use a workstation with a minimum of 512 megabytes (MB) of RAM.

  • Allocate at least 2 GB of virtual memory, and a 2 GB page file. If the amount of virtual memory on the computer on which you are running the repository merge is too low, performance degrades significantly.

  • If necessary, increase the swap space, using the Control Panel System applet, and then restart the development workstation before proceeding.

  • Allocate plenty of 32K work space for the Sort utility.

  • Make sure you have a high-performing network connection.

    Note: A slow network connection significantly increases the time required for the repository merge.

  • Close all other applications.

  • Close all Siebel services.

• Defragment the disk. Fragmentation significantly affects system performance.

• On the workstation, check that the environment variable SIEBEL_LOG_EVENTS is set to zero. To check, enter the following command at the MS DOS prompt:

  echo %SIEBEL_LOG_EVENTS% 
  

  If the command returns a value other than zero, you must set the SIEBEL_LOG_EVENTS variable to zero by performing the following steps:

  • Close Siebel Tools and any other Siebel client applications.

  • From the Start menu, select Settings, Control Panel, System, and then Environment.

  • In the Environment dialog box, in the System Variables box, select SIEBEL_LOG_EVENTS. Enter 0 in the Value box, and click Set. Click OK.

  • Relaunch Siebel Tools. The new setting becomes active.

    Note: The steps required to set this variable can vary depending on the operating system you are using.

• Optimize your database, because database performance can cause the repository merge to slow down considerably. Check the following:

  • Make sure that temporary table space has enough space allocated.

  • Make sure the database has enough space allocated.

  • Make sure that the topmost logging applet in tools has no extra rows from previous repository merge runs when starting the repository merge.

  • Make sure that the database is not loaded with users when the repository merge is run; no other users must be connected.