Upgrade Guide for UNIX > Upgrading Without a Development Environment >

Upgrading Without a Development Environment

If you are upgrading without a development environment, upgrade a test environment (using a copy of your production database) before you upgrade your production environment. After you have verified that the upgrade was successful in a test environment, you can safely upgrade your production environment.

Complete the following steps to upgrade your production repository and database schema.

CAUTION:  This procedure overwrites all customizations. Do not attempt this procedure if you have a development environment or if you have customizations or configuration changes to your Siebel deployment.

To upgrade without a development environment

  1. Upgrade your test environment. Navigate to /dbsrvr/common and locate the mstrep.dat file. Copy the mstrep.dat file and rename it custrep.dat. Place the custrep.dat file in the /dbsrvr/platform directory.
  2. Use the configuration utility to upgrade the Siebel database schema on your test environment, as instructed in Upgrading the Siebel Database Schema.
    1. Specify parameters you listed in the Upgrade Planning Worksheet.
    2. Set the following parameter as shown:

    Environment Type = "Production"

    NOTE:  You might need to change the ODBC data source to point to your test database before upgrading the Siebel database schema and the custom database schema.

  3. Use the configuration utility to upgrade the custom database schema on your test environment, as instructed in Upgrading the Custom Database Schema.
    • Specify parameters you listed in the Upgrade Planning Worksheet.
  4. Review the upgrade log files to verify that no unacceptable errors are reported. See Reviewing the Upgrade Log Files.

    NOTE:  You should save log files from the SiebSrvr\Log directory into a Zip file so that you can review them later. If you do not save them, they are moved to the SiebSrvr\Log archive directory and removed when the machine is rebooted or Siebel Server services are restarted.

    If you find errors that are not included in the errors.rtf file in the DBSRVR_PLTFRM_ROOT directory, contact Siebel Technical Support.

CAUTION:  Before you begin the upgrade of your production environment, verify that there are no repositories named "Siebel Repository" or "New Customer Repository" in your database.

  1. Upgrade your production environment. Use the configuration utility to upgrade the Siebel database schema on your production environment, as instructed in Upgrading the Siebel Database Schema.
    1. Specify parameters you listed in the Upgrade Planning Worksheet.
    2. Make sure that the following parameter is set as shown below:

    Environment Type = "Production"

    NOTE:  You might need to change the ODBC data source to point to your production database before upgrading the Siebel database schema and the custom database schema.

  2. Use the configuration utility to upgrade the custom database schema on your production environment, as instructed in Upgrading the Custom Database Schema.
    • Specify parameters you listed in the Upgrade Planning Worksheet.
  3. Verify that no unacceptable errors are reported in the error logs. See Reviewing the Upgrade Log Files.


 Upgrade Guide for UNIX
 Published: 20 October 2003