Siebel Database Upgrade Guide > Overview of Performing a Siebel Database Upgrade >

Process of Upgrading a Siebel Production Test Environment

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

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 when doing the upgrade.

NOTE:  Links to other topics in this guide are provided throughout this chapter. These links are meant to provide additional information that cannot be provided in these brief overviews. You must, however, perform the upgrade in the proper order. For information on general planning, see this chapter as well as Siebel Database Upgrade Planning, and Application Planning for a Siebel Upgrade. To begin the process of upgrading your Siebel database, see Preparing for Siebel Database Upgrade, then refer to each subsequent chapter after that.

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

NOTE:  If you are performing a Production Test environment upgrade on IBM z/OS, then see Siebel Database Upgrade Guide for DB2 for z/OS.

Search for Articles on My Oracle Support

• Check My Oracle Support for recently published articles regarding the upgrade. For more information, see Naming Conventions Used in This Guide.

Upgrade the Servers

Verify you have identified all the maintenance releases, and fix packs required for the upgrade. These requirements are located in the applicable Siebel Maintenance Release Guide on My Oracle Support

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 computer 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, then 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, then you can run a script to migrate configuration parameters to the upgraded Siebel Enterprise.

Upgrade Third-Party Software

• Upgrade third-party software as required due to dependencies on Oracle's Siebel software or other installed software. For example, you might need to upgrade the following software:

  Operating system software. Some database upgrades require newer versions of AIX or Windows.

Upgrade the RDBMS

• 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.

    NOTE:  For Siebel CRM product releases 8.1.1.9 and later and for 8.2.2.2 and later, the system requirements and supported platform certifications are available from the Certification tab on My Oracle Support. For information about the Certification application, see article 1492194.1 (Article ID) on My Oracle Support.

  • For information on how upgrading your RDBMS affects the upgrade process, see About Upgrading Your RDBMS in the Siebel Environment.

Perform Preupgrade 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 Preparing for Siebel Database Upgrade.

Perform Preupgrade 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% before the upgrade if possible.

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

Perform Preupgrade 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.

Perform Preupgrade 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.

Perform Preupgrade Tasks for Application Data

1. Perform the tasks in 477519.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 521. The following table shows the applicability of the tasks in the article.

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

Prepare the Siebel Database for Upgrade

1. Refer to 477772.1 (Article ID) on My Oracle Support. 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:
   • Custom SRF file.
   • Reports files.
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, then 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, then ignore this step.)

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

Upgrade the Siebel Database (upgrep and upgphys)

1. Run the Database Configuration Wizard:
   • Preparing to Run the Siebel Database Configuration Wizard.
   • Running the Siebel Database Configuration Wizard Under Windows.
   • Running the Siebel Database Configuration Wizard Under UNIX.

     Choose the following settings:

   • Upgrade Options: Upgrade Siebel Database Schema (upgrep and upgphys)
   • Environment Type: Production Test
2. Refer to 475427.1 (Article ID) on My Oracle Support for any instructions specific to your upgrade scenario. This document was previously published as Siebel Alert 1322.
3. Resume the upgrade: Starting the Siebel Upgrade Wizard.
4. Review the upgrade logs and resolve errors:
   • Reviewing Siebel Upgrade Log Files for Errors.
5. If the upgrade contains unacceptable errors, then 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, then 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.

Perform Postupgrade Tasks for Database and File System

1. Perform the tasks in Postupgrade Tasks for the Siebel Database.
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, then review the database and import the data as desired.
4. Generate a Siebel Remote database template file. See Siebel Remote and Replication Manager Administration Guide.
5. Run database statistics.

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

Perform Postupgrade Tasks for Applications Configuration

1. Perform the tasks in Postupgrade Tasks for Siebel Business 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 Enterprise Application Integration, then verify that the integrations are configured correctly. For information on EAI, see Overview: Siebel Enterprise Application Integration.
5. If you have used Siebel Enterprise Integration Manager to set up batch processing jobs, then verify Siebel Enterprise Integration Manager is configured correctly. For information on Siebel Enterprise Integration Manager, see Siebel Enterprise Integration Manager Administration Guide.
6. If you customized style sheet or Web template files in the previous release, then reimplement those customizations in the new release as desired.

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

Perform 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