Upgrade Guide for DB2 UDB for z/OS and OS/390 > How to Perform the Upgrade >

Process of Upgrading a Production Environment

Upgrades: All upgrades.

Environments: Production environment only.

This process is part of a road map. See Road Map for Performing the Upgrade.

This topic lists the tasks required to transition your development 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.

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 on Siebel SupportWeb under Product Documentation > Maintenance Release Guides.

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

1. Install Siebel Tools on development workstations. Keep at least one copy of the previous version of Siebel Tools. You will need it to perform repository operations before the repository merge.
2. Install the Siebel Gateway Name Server, Siebel Servers, and Siebel Web Server Extension (SWSE). In many cases, you do not have to uninstall the Siebel Servers or SWSE before installing the new versions.
3. Install the Siebel Database Server files on the Siebel Server you will use to perform the upgrade.
4. Install language packs for your currently deployed languages and any new languages.

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

Upgrade Third-Party Software

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

• If required, upgrade the RDBMS version. Refer to the vendor's documentation to perform the upgrade. For information on supported RDBMS systems, see System Requirements and Supported Platforms on Siebel SupportWeb.

Preupgrade Tasks for the Siebel Database Upgrade

These steps apply to all database types.

1. Review Siebel Technical Notes and Siebel Alerts on upgrading to the current release. Make revisions to the upgrade process as required. See Important Upgrade Planning Resources.
2. Review Technical Note 521. It contains important changes to database records and repository objects that must be made during the upgrade. See Important Upgrade Planning Resources.
3. Review guidelines for configuring the RDBMS. See the Siebel Installation Guide for the operating system you are using.
4. Verify all developers have checked in their projects.
5. Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
6. Stop the Siebel Server and the Siebel Gateway Name Server.
7. Verify there are no open database connections.
8. Preparing Tables and Views for Upgrade.
9. Preparing Custom Indexes for Upgrade.
10. Exporting Interface Table Data.
11. Preserving Dock Objects and Visibility Rules.
12. Verifying Database Server Configuration.
13. Securing AIX Memory Allocation Segment Space.
14. Creating Storage Groups.
15. Preparing the Storage Layout of the Schema.
16. Reviewing Tablespace Size.
17. Backing Up the Database.
18. Adding a Siebel User.

Preupgrade Tasks for DB2 UDB for z/OS

1. Prerequisites for a Development Upgrade.
2. Checking In Development Repository Projects.
3. Saving Interface Table Data.
4. Upgrading Your DB2 Software.
5. Preparing EIM Tables for Upgrade.
6. Preparing for Intersection Table Maintenance and Deduplication.
7. Determining Which Template File was Used During an Extract or Merge.
8. Disabling Customized Triggers.
9. Dropping Customized Views.
10. Preparing the Development Environment Repositories for Upgrade.

Preupgrade Tasks for Application Data

1. Preparing Workflow Processes for Upgrade.
2. Preparing Mobile and Dedicated User Data for the Database Upgrade.

The remaining tasks are optional depending on currently installed Siebel products and whether the data in the development environment needs to be preserved or upgraded. Review and perform these tasks as necessary.

3. Setting Up Campaign Status Values for Siebel Marketing Upgrade.
4. Preparing Address Data for Upgrade.
5. Preparing Products for Upgrade.
6. Preserving Marketing Segment Descriptions.
7. Preparing Siebel eChannel Data for Upgrade.
8. Preparing Forecasting Data for Upgrade.
9. Preparing Products and Quotes for Upgrade.
10. Verifying Household Data Integrity.
11. Preparing Financial Services Application Tables for Upgrade.
12. Preparing Siebel Configurator Data for Upgrade.

Prepare the Siebel Database for Upgrade

1. Verify you have a current backup of the production environment database.
2. On the Siebel Server you used to upgrade the development environment database, create an ODBC to connect to the production environment database.
3. Disconnect the Siebel Server from the development environment database.
4. Connect the Siebel Server to the production environment database.
5. Navigate to DBSRVR_ROOT\common (UNIX: DBSRVR_ROOT/common) and verify that the file sqlgen.usg exists.

   This file contains a record of when the SQL generator was run. When you run the Database Server Configuration utility, if this file exists, no SQL commands are generated.

   CAUTION:  If this file does not exist, do not run the Database Server Configuration utility. It will overwrite the SQL files used to upgrade your development environment database. Contact Siebel Technical Support for guidance on proceeding with the upgrade.

Upgrade the Siebel Database Schema (upgrep)

1. Run the Database Server Configuration utility:
   • Preparing to Run the Database Server Configuration Utility.
   • Running the Database Server Configuration Utility Under Windows.
   • Running the Database Server Configuration Utility Under UNIX.

     When running the Database Server Configuration Utility, choose the following settings:

     • Upgrade Options: Upgrade Siebel Database Schema (upgrep + upgphys)
     • Environment Type: Production
   1. Enter the information for the production environment instead of the development environment.
   2. When prompted whether you want to run the Siebel Upgrade Wizard, answer No and exit.

      This updates the master UCF file with the production environment configuration. When you run the Siebel Upgrade Wizard, the SQL commands will be executed on the production environment database.

2. Upgrade the production environment database. See Running the Siebel Upgrade Wizard.

   The Siebel Upgrade Wizard uses the SQL commands generated for the development environment to upgrade the production environment.

3. Reviewing Upgrade Log Files for Errors.
4. If the upgrade contains unacceptable errors, do the following:
   1. Restore the backup of the database.
   2. Correct the errors.
   3. Rerun the Database Server Configuration utility.
5. Manually Archiving Upgrade Log Files.

Upgrade the Siebel Database Schema (upgphys)

1. Run the Database Server Configuration utility:
   • Preparing to Run the Database Server Configuration Utility.
   • Running the Database Server Configuration Utility Under Windows.
   • Running the Database Server Configuration Utility Under UNIX.

     When running the Database Server Configuration Utility, choose the following settings:

     • Upgrade Options: Upgrade Siebel Database Schema (upgrep + upgphys)
     • Environment Type: Production
2. Reviewing Upgrade Log Files for Errors.
3. If the upgrade contains unacceptable errors, do the following:
   1. Restore the backup of the database.
   2. Correct the errors.
   3. Rerun the Database Server Configuration utility.
4. Manually Archiving Upgrade Log Files.
5. Installing New License Keys After Upgrade.
6. Back up the upgraded database.

Postupgrade Tasks for Environment Setup

1. Updating File System Attachments.
2. Generate a Siebel Remote database template file. See Siebel Remote and Replication Manager Administration Guide and Upgrading Siebel Mobile and Dedicated Web Clients.
3. Generate database extracts for all Regional Servers in the deployment. See Upgrading Regional Servers.
4. Reset upgrade-specific parameters back to their defaults. See Resetting Database Server Configuration Parameters.
5. Checking for Inactivated EIM Table Columns.
6. Run database statistics. For more information, see Generating RUNSTATS.

NOTE:  The production environment is now upgraded. The remaining sections deal with configuration and validation tasks.

Postupgrade Tasks for Configuration

1. If you exported data from interface tables before the upgrade, review the database and import the data as desired.
2. Upgrading to RC2 or AES Encryption.

Configure for Globalization

1. Upgrading to the Symbolic String Model.
2. Setting Up Your Environment to Support Global Time Zone.

Deploy Workflows

To perform these tasks, see Siebel Business Process Designer Administration Guide.

1. Activate and deploy workflows. See Siebel Business Process Designer Administration Guide.
2. Upgrading Seeded Workflows.
3. Upgrading Inbound Workflows.

Verify Application Integration

1. Verify that EAI and EIM integrations are set up correctly. For information on using EAI and EIM, see Overview: Siebel Enterprise Application Integration and Siebel Enterprise Integration Manager Administration Guide.
2. Updating Enterprise Application Integration (EAI) After Upgrade.

Postupgrade Tasks for Application Administration

1. Review the results of the Person and Organization merge. Make configuration changes as required.
2. Generating Reporting Relationships After Upgrade.
3. Validating Dock Objects and Rule Definitions.
4. Perform the tasks in Postupgrade Tasks for Applications to prepare for system testing.

Perform System Tests

1. Thoroughly test all applications.

Deploy to Users

1. 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 eBusiness Applications.
2. Use the Siebel Application Deployment Manager to migrate administrative data such as LOVs and responsibilities from development to production. See Going Live with Siebel eBusiness Applications.
3. Use Siebel Packager to create language packs for remote installation. See Going Live with Siebel eBusiness Applications.
4. Use Siebel Anywhere to create installation kits for deployment. See Siebel Anywhere Administration Guide.
5. Generate a Siebel Remote database template. See Siebel Remote and Replication Manager Administration Guide.
6. Set up database extraction for Siebel Mobile Web Clients. See Siebel Remote and Replication Manager Administration Guide.