Siebel Database Upgrade Guide > How to Perform a Siebel Database Upgrade >

Process of Upgrading a Siebel Production Test Environment

Upgrades from: All Supported Siebel releases.

Environments: Production test environment only. Does not apply to production environment.

Platforms: Windows and UNIX only. This topic does not apply to IBM z/OS.

This process is part of a roadmap. See Roadmap for Performing a Siebel Database Upgrade.

This topic lists the steps required to upgrade a production test environment to the current release. Print this topic and use it as a checklist for doing the upgrade.

The topic is divided into sections, each containing a list of numbered steps. Complete each section in the order shown.

CAUTION:  Do not use this topic to perform a production test environment upgrade on IBM z/OS. Instead, refer to Siebel Database Upgrade Guide for DB2 UDB for z/OS.

Search for Bulletins and Alerts on OracleMetalink 3

  1. Check OracleMetalink 3 for recently published Bulletins and Alerts regarding the upgrade. For more information, see About Siebel Upgrade Planning Resources.

Upgrade the Servers

Verify you have identified all the maintenance releases, Fix Packs, and quick-fix patches required for the upgrade. These requirements are located in the applicable Siebel Maintenance Release Guide on OracleMetalink 3

CAUTION:  Do not install a new Siebel Database as part of upgrading the Siebel Enterprise.

To perform the following steps, see the Siebel Installation Guide for the operating system you are using.

  1. Upgrade the Gateway Name Server, Siebel Servers, and Siebel Web Server Extension (SWSE).

    For information upgrading these Siebel Enterprise components, see Siebel Installation Guide for the operating system you are using.

  2. Install the Siebel Database Server files on the Siebel Server you will use to perform the upgrade. You only need to install the database server files for the database type that you are upgrading.

    NOTE:  You need only to install a new Siebel Server software if you are using a different machine from that on which you performed the Production Test Upgrade. If you are using the same Siebel Server installation as for the Production Test Upgrade, the existing files can be leveraged instead.

  3. Install language packs for your currently deployed languages and any new languages.
  4. If you have customized the configuration of Enterprise components, such as Siebel Servers, you can run a script to migrate configuration parameters to the upgraded Siebel Enterprise. See Going Live with Siebel Business Applications.

Upgrade Third-Party Software

  1. Upgrade third-party software as required due to dependencies on Oracle's Siebel software or other installed software. For example, you may need to upgrade the following software:
    • Actuate Server (Siebel Reports Server).
    • Operating system software. Some database upgrades require newer versions of AIX or Windows.

Upgrade the RDBMS

  1. If required, upgrade the RDBMS version. Refer to the vendor's documentation to perform the upgrade:
    • For information on supported RDBMS systems, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.
    • For information on how upgrading your RDBMS affects the upgrade process, see About Upgrading Your RDBMS in the Siebel Environment.

Pre-Upgrade Tasks for the Siebel Database

These steps apply to all database types.

  1. Review guidelines for configuring the RDBMS. See the Siebel Installation Guide for the operating system you are using.
  2. Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
  3. Perform the tasks in Basic Database Preparations for a Siebel Upgrade.

Pre-Upgrade Tasks for IBM DB2

  1. Perform the tasks in Preparing an IBM DB2 Database for a Siebel Upgrade.
  2. Make sure that runstats is current in your environment and that tables with clustering indexes are not out of cluster. Reorganize any tables that are out of cluster or that are clustered less than 90% in advance of the upgrade if possible.

    Table maintenance should be aggressively pursued prior to the upgrade to ensure that your system is in optimal condition. The same general consideration should also be kept in mind with regard to respository tables.

Pre-Upgrade Tasks for Oracle Databases

  1. Perform the tasks in Preparing an Oracle Database for a Siebel Upgrade.
  2. Run the Oracle Analyze command on the Siebel Database. Highly fragmented indexes can cause the upgrade to fail.

Pre-Upgrade Tasks for Microsoft SQL Server

  1. Perform the tasks in Preparing a Microsoft SQL Server Database for a Siebel Upgrade.
  2. Run Microsoft SQL Server statistics. This will improve upgrade performance.

Pre-Upgrade Tasks for Application Data

  1. Perform the tasks in Bulletin 477519.1 (Doc ID) on OracleMetalink 3. This document was previously published as Siebel Technical Note 521. The following table shows the applicability of the tasks in the Bulletin.

Location and amendment of S_VIEW_WTMPL_IT.ITEM_NUM records

Development, production test, production

Update multi-value group (MVG) and association list applets

Development only

Update unnamed controls in applet web template items

Development only

  1. Perform the tasks in Preparing Siebel Application Data for Upgrade.

Prepare the Siebel Database for Upgrade

  1. Refer to Bulletin 477772.1 (Doc ID) on OracleMetalink 3. This document was previously published as Siebel Technical Note 586, and includes instructions on how to set up the Siebel Database and Siebel Servers in the production test environment.
  2. Stop the Siebel Servers and the Siebel Gateway Name Server.
  3. Close all database connections. The only database connection must be the account performing the upgrade.
  4. Copy application files to the environment:
  5. Copy the custrep.dat and schema.ddl files to the environment. See Moving the Siebel Repository Files

    If you have made changes to the Siebel Repository since performing the development upgphys, you must regenerate the schema.ddl and custrep.dat files. See Regenerating the Siebel Repository Definition Files.

  6. Verify the production test database is either a copy of the current production database or has the same topology and amount of data.

    This is important for effective upgrade tuning before performing the production upgrade.

  7. Back up the production test environment database. (If you backed up the database as part of an RDBMS upgrade, ignore this step.)

    To do upgrade tuning, you will restore this database and perform test-upgrades on it.

Run the Upgrade Utilities in Prepare for Production Mode

  1. (Optional) Changing the Siebel Database Configuration Utilities Language.
  2. Run the Database Configuration Wizard:
  3. Review the following topic and perform the procedure if applicable: Identifying and Dropping Obsolete Indexes for a Siebel Upgrade.

Upgrade the Siebel Database (upgrep and upgphys)

  1. Run the Database Configuration Wizard:
  2. Edit generated SQL files as required by Bulletins or Alerts on OracleMetalink 3, Siebel Release Notes on OracleMetaLink 3 or other publications.
  3. Resume the upgrade: Starting the Siebel Upgrade Wizard.
  4. Review the upgrade logs and resolve errors:
  5. If the upgrade contains unacceptable errors, do the following:
    1. Restore the backup of the database.
    2. Correct the errors.
    3. If errors occurred because you entered incorrect information in the Database Configuration Wizard, see Regenerating SQL Files for a Siebel Upgrade.
    4. Rerun the Database Configuration Wizard.
  6. Manually Archiving Siebel Upgrade Log Files.
  7. Installing New Siebel License Keys During an Upgrade.
  8. Back up the upgraded database.

Postupgrade Tasks for Database and File System

  1. Perform the tasks in Postupgrade Tasks for the Siebel Database and File System.
  2. Reset upgrade-specific database and database server parameters back to their recommended settings for production. See Siebel Installation Guide for the operating system you are using for recommended parameter settings.
  3. If you exported data from interface tables before the upgrade, review the database and import the data as desired.
  4. Upgrade Planning for Siebel RC2 or AES Encryption.
  5. Generate a Siebel Remote database template file. See Siebel Remote and Replication Manager Administration Guide.
  6. Run database statistics.

NOTE:  The upgrade is complete. The remaining topics deal with configuration and validation tasks.

Postupgrade Tasks for Applications Configuration

  1. Perform the tasks in Postupgrade Tasks for Siebel Applications.
  2. Verify the function of interfaces in integrated applications.
  3. Activate and deploy workflows.
  4. If you have set up integrations for transferring data to or from third-party applications using Siebel EAI, verify the integrations are configured correctly. For information on EAI, see Overview: Siebel Enterprise Application Integration.
  5. If you have used EIM to set up batch processing jobs, verify EIM is configured correctly. For information on EIM, see Siebel Enterprise Integration Manager Administration Guide.
  6. If you customized style sheet or Web template files in the previous release, reimplement those customizations in the new release as desired.

    Carefully review the UI in the new release before reimplementing customizations to these files.

System Tests

  1. Use available test data to perform unit testing. Validate the operation of the application in the following areas:
    • User interface
    • Data interfaces
    • Integrity of migrated data
    • Workflow function
Siebel Database Upgrade Guide Copyright © 2008, Oracle. All rights reserved.