Siebel Database Upgrade Guide for DB2 UDB for z/OS > How to Perform a Siebel Database Upgrade >

Process of Upgrading a Siebel Production Environment

Upgrades: All upgrades.

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

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

This topic lists the tasks required to transition your production test environment to production. Print this topic and use it as a checklist for doing the upgrade.

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

Review Siebel Technical Notes and Alerts on My Oracle Support

1. Check My Oracle Support for Siebel Alerts and Technical Notes regarding upgrade.
2. Review the chapter in Siebel Database Upgrade Guide that describes Siebel database and UI upgrade planning. This chapter lists important publications and resources for performing an upgrade.

Upgrade Third-Party Software

3. Upgrade third-party software as required due to dependencies on 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 Servers

Verify you have identified all the maintenance releases, Fix Packs, and quick-fix patches required for the upgrade. These requirements are documented in 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 and Implementing Siebel Business Applications on DB2 for z/OS.

4. Install the Siebel 8.0 Gateway Name Server, Siebel Servers, and Siebel Web Server Extension (SWSE).

   The upgraded Siebel Servers will not work correctly with the RDBMS server until after you have upgraded the Siebel database to the new release.

5. Install the Siebel Database Configuration Utilities files on the Siebel Server you will use to perform the upgrade.
6. Install language packs for your currently deployed languages and any new languages.
7. If you have customized the configuration of Enterprise components, such as Siebel Servers, you must migrate the customizations to the upgraded environment. See Going Live with Siebel Business Applications.

Upgrade the RDBMS

8. If required, upgrade your version of DB2 for z/OS. Refer to the IBM documentation to perform the upgrade. For information on supported RDBMS systems and versions, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.

Identify and Resolve Duplicate Row IDs

9. 6.2.1 upgrades only: Identifying and Resolving Duplicate Row IDs.

   After you install the Siebel Database Configuration Utilities software, but before you upgrade to this release, you must identify and resolve any duplicate row IDs in your Siebel database.

Preupgrade Tasks for the Siebel Database

10. Review guidelines for configuring DB2 for z/OS. See Implementing Siebel Business Applications on DB2 for z/OS.
11. Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
12. Stop the Siebel Servers.
13. Verify there are no open database connections.
14. Prepare the storage control file to use in the upgrade. See Preparing the Storage Layout of the Schema.
15. Perform the applicable tasks in the following:
    • Basic Database Preparations for a Siebel Upgrade
    • The chapter of the Siebel Database Upgrade Guide that describes the basic database preparations for a Siebel upgrade.

Preupgrade Tasks for Application Data

16. Perform the tasks in 477519.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 521.
17. Perform the relevant tasks in the following:
    • Preparing Siebel Application Data for Upgrade
    • The chapter of the Siebel Database Upgrade Guide that describes how to prepare Siebel application data for upgrade.

      Some of these tasks are optional, depending on the currently installed Siebel products and your upgrade path. Review and perform these tasks as necessary.

Preupgrade Tasks for a Production Environment Upgrade

18. Copy application files to the environment:
    1. Custom SRF file.
    2. Reports files.
    3. Custom Web templates and style sheets. See the topic on Copying UI Files to a New Siebel Environment in the chapter of the Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge.
19. About Moving the Customized Repository and Schema Definition Files.
20. Preparing for a No-Development-Environment Siebel Upgrade. If you do not have a development environment, see Preparing for a No-Development-Environment Siebel Upgrade for information on this task.

Upgrade the Siebel Database Schema (upgrep + upgphys)

If you have completed a production test upgrade and have tuned the SQL and JCL upgrade files on the z/OS host, you can use these files to perform the target database upgrade in the production environment. This approach has several advantages:

• You do not have to generate upgrade files in the production environment and then manually transfer customizations to them from the production test environment.
• You do not have to run the Database Configuration Wizard in Prepare for Production mode again.
• You do not have to run the zSeries Staging of Files for Upgrade process using the Database Configuration Wizard to create the staging database and to generate upgrade files again.
• With some exceptions, you do not have to perform database-related configuration tasks required by Release Notes or Alerts again.

NOTE:  Before using the tuned upgrade files that you generated in the production test environment, you must edit the upgrade files to change the production test environment values to production environment values.

21. Verify you have a current backup of the production environment database.
22. On the Siebel Server you used to upgrade the production test environment, create an ODBC to connect to the production environment database.
23. Edit the tuned upgrade files you generated during the production test environment upgrade. Replace any values in the upgrade files that are specific to the production test environment with production environment values. You may need to change the following values in the upgrade files:
    • Host/LPAR name where the target database resides
    • DB2 subsystem name of the target database
    • Schema/Tableowner qualifier name on the target database
    • ODBC data source name of the target database

      You can edit the upgrade files using any utility that allows you to edit partitioned data sets (PDSs). For advice on editing upgrade files, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.

24. Upgrade the target database using the tuned upgrade files, which now contain production environment information, by performing the following tasks:
    1. Creating and Loading Siebel Log Tables
    2. Applying Additive Upgrade Changes to the Target Database
    3. Renaming the Production Environment Repository
    4. Performing the In-Place Target Database Upgrade
25. Extract the storage control file from the target database using the Database Configuration Wizard as follows:
    • Specify the following values when prompted to do so:
      • Extract Options: Extract from Catalog
      • Storage Control File: Specify the name of the storage control file to be extracted, for example, storage_postupg.ctl.
    • Make sure you specify values for the target database when prompted for the names of the schema Qualifier, ODBC data source, and database user name and password.

      The procedure to extract a storage control file using the Extract from catalog option is described in Implementing Siebel Business Applications on DB2 for z/OS. The extracted target database storage control file is used as input to the upgphys upgrade process.

26. Upgrade the repository and import seed data. See Upgrading the Repository and Importing Seed Data.
27. Performing Intersection Table Maintenance.
28. About the Siebel Upgrade Log Files.
29. If the upgrade contains unacceptable errors, do the following:
    1. Restore the backup of the database.
    2. Correct the errors.
    3. Rerun the Database Configuration Wizard.
30. 6.2.1 upgrades only: If you have multilingual deployments, perform the steps in 477094.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 447. This document describes how to import language-specific repository strings and seed data into the upgrade repositories.
31. Manually Archiving Upgrade Log Files.
32. Back up the upgraded production database.
33. Deleting Redundant Upgrade Files.

Postupgrade Tasks for Database and File System

34. Perform the relevant tasks in the following:
    • Postupgrade Tasks for Siebel Database and File System
    • The chapter of the Siebel Database Upgrade Guide that describes the postupgrade tasks for the Siebel database and file system.
35. 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 and Implementing Siebel Business Applications on DB2 for z/OS for recommended parameter settings.
36. If you exported data from interface tables before the upgrade, review the database and import the data as desired.
37. Upgrading to Siebel RC2 or AES Encryption. See the chapter of the Siebel Database Upgrade Guide that describes Siebel database and UI upgrade planning.
38. Generate database statistics for new or rebuilt tables and indexes. Determine whether any tables need to be reorganized by running RUNSTATS with the Report Only option specified. For more information about running statistics, see Generating RUNSTATS Jobs.

The production environment is now upgraded. The remaining topics in this chapter deal with configuration and validation tasks.

Postupgrade Tasks for Applications Configuration

39. Review the results of the Person and Organization merge, if applicable. Make configuration changes as required. For further information, see the topic on the Party Model in the chapter of the Siebel Database Upgrade Guide that describes Siebel database and UI upgrade planning.
40. Perform the tasks in the following:
    • Postupgrade Tasks for Siebel Applications
    • The chapter of the Siebel Database Upgrade Guide that describes the postupgrade tasks for Siebel applications.
41. Activate and deploy workflows. To perform these tasks, see Siebel Business Process Framework: Workflow Guide.
42. 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 using EAI, see Overview: Siebel Enterprise Application Integration.
43. If you have used EIM to set up batch processing jobs, verify EIM is configured correctly. For information on using EIM, see Siebel Enterprise Integration Manager Administration Guide.
44. If you customized style sheet or web template files in the previous release, you have to implement those customizations again in the new release, if desired.

Perform System Tests

45. Use available test data to perform unit testing. Validate application function in the following areas:
    • User interface
    • Data interfaces
    • Integrity of migrated data
    • Workflow function

Deploy to Users

46. Upgrade your Siebel Mobile and Developer Web Clients. See the Siebel Installation Guide for the operating system you are using for further information.
47. If you have customized the configuration of Siebel Enterprise Server components, such as Siebel Servers, you must manually enter the customizations in the upgraded environments. See Going Live with Siebel Business Applications.
48. Use Siebel Packager to create language packs for remote installation. See Going Live with Siebel Business Applications.
49. Use Siebel Anywhere to create installation kits for deployment. See Siebel Anywhere Administration Guide.
50. Generate a Siebel Remote database template. See Siebel Remote and Replication Manager Administration Guide.
51. Set up database extraction for Siebel Mobile Web Clients. See Siebel Remote and Replication Manager Administration Guide.