Bookshelf Home | Contents | Index | PDF     

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

Process of Upgrading a Siebel Development Environment

Upgrades: All upgrades.

Environments: Development environment only.

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

This topic lists the steps required to upgrade a Siebel development 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.

Steps that apply only to upgrades from Release 6.2.1 are marked as such.

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

  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 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:

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

  2. Install the Siebel Database Configuration Utilities files on the Siebel Server you will use to perform the upgrade.
  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 must migrate the customizations to the upgraded environment. See Going Live with Siebel Business Applications.

Upgrade the RDBMS

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

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

  1. Review guidelines for configuring DB2 for z/OS. See Implementing Siebel Business Applications on DB2 for z/OS.
  2. Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
  3. Stop the Siebel Servers.
  4. Prepare the storage control file to use in the upgrade. See Preparing the Storage Layout of the Schema.
  5. Perform relevant tasks in:
  6. Migrating Siebel Repository Objects to the Standard UI. For information on this topic, see the chapter in the Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge.

Preupgrade Tasks for a Development Environment Upgrade

  1. Perform the tasks in Preparing a Development Environment for a Siebel Upgrade.
  2. Rename the Siebel Repository. For information on this step, see the chapter in the Siebel Database Upgrade Guide that describes upgrading the Siebel database.

Preupgrade Tasks for Application Data

  1. Perform the tasks described in the following documents:
    • 477519.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 521.
    • 477254.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 481.
  2. Perform the relevant tasks in:
    • 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.

Preparing Developers for the Upgrade

  1. Back up the development database.
  2. Verify that all developers have checked in their projects and that all projects are unlocked.
  3. Verify that all developers have disconnected from the database. The only open connection should be the account that is performing the upgrade.
  4. Install the new Siebel Tools and license keys 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.
  5. Perform all remaining tasks with the new Siebel Tools, unless stated otherwise.

Upgrade Siebel Database Schema (upgrep)

  1. (Optional) Changing the Siebel Database Configuration Wizard Language. For information on this topic, see the chapter of the Siebel Database Upgrade Guide that describes how to upgrade the Siebel database.
  2. Create the staging database by performing the following tasks:
    1. Required Tasks before Creating the Staging Database
    2. Creating the Staging Database Schema DDL Files.
    3. Transferring the Staging DDL to the z/OS Host.
    4. Preparing the z/OS Host Upgrade Environment and Creating the Staging Database.
    5. Removing Interface Tables and Triggers.
  3. Generate the Upgrade Files by performing the following tasks:

    NOTE:  Edit the generated files as required by Siebel Technical Notes, Alerts, Release Notes or other publications before transferring them to the z/OS host.

    1. Prerequisite Tasks for Generating the Upgrade Files
    2. Restarting the Siebel Upgrade Wizard After Pauses
    3. Preparing the Additive Schema and JCL Files on the z/OS Host.
    4. Restarting the Siebel Upgrade Wizard After Pauses
    5. Preparing and Executing the Non-Additive Schema and JCL Files on the z/OS Host.
    6. Restarting the Siebel Upgrade Wizard After Pauses
    7. Processing the Index Schema File.
    8. Building JCL Templates for the Target Database.
  4. Upgrade the target database by performing the following tasks:
    1. Creating and Loading Siebel Log Tables
    2. Process of Upgrading the Target Database
    3. Performing the In-Place Target Database Upgrade
  5. Upgrade the repository and import seed data. See Upgrading the Repository and Importing Seed Data.
  6. About the Siebel Upgrade Log Files.
  7. 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.
  8. Installing New License Keys After Upgrade.
  9. 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.
  10. Back up the upgraded database repository.

Prepare for Repository Merge

  1. Perform relevant tasks in the chapter of the Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge.

    NOTE:  Review the topic that describes how to configure Siebel Repository objects to inherit upgrade behavior.

  2. About Backing Up the New Customer Repository or Database Schema.
  3. 6.2.1 upgrades only: Running the Repository Preparation Wizard on a Release 6.2.1 Repository.
  4. Execute the REORG utility on tables that receive a large number of inserts during the repository import process. For further information about reorganizing tables, see About Reorganizing Tables Before the Repository Merge.
  5. Run database statistics on the Siebel database. For further information on running database statistics, see Generating RUNSTATS Jobs. Running statistics on the Siebel database improves merge performance.

    If upgrading from Release 7. 7 or Release 7.8.x, run statistics specifically on the S_SYM_STR and SYM_STR_INT tables. If you are upgrading from a pre-7.7 release, the S_SYM_STR and SYM_STR_INT tables are not populated until the merge is completed so you do not need to run statistics on them at this point.

Perform Repository Merge

CAUTION:  The Repository merge process cannot be stopped and restarted so make sure you have backed up the database schema or the New Customer Repository before starting the merge.

  1. Performing a Siebel Repository Merge.
  2. Review the Siebel Repository merge logs. For information on this task, see the chapter of the Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge.
  3. If the repository merge contains unacceptable errors, do the following:
    1. Restore the backup of the database or New Customer Repository.
    2. Correct the errors.
    3. Rerun the repository merge.
  4. Review Siebel Repository Object Property Conflicts.

    For information on this task, see the chapter of the Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge.

  5. Run the Siebel Postmerge Utilities.

    For information on this task, see the chapter of the Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge.

  6. Generate Siebel EIM Temporary Columns.

    For information on this task, see the chapter of the Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge.

  7. Generate database statistics for new tables and new indexes using the RUNSTATS utility. Your DBA can check the system catalog to determine the database objects that do not have statistics.

    For further information on generating database statistics, see Generating RUNSTATS Jobs.

  8. Back up the Siebel database.

Migrate 6.2.1 Customizations

6.2.1 upgrades only: The steps in Migrate 6.2.1 Customizations apply only to upgrades from Release 6.2.1.

  1. Identifying What Will Be Migrated.
  2. Exposing Hidden Properties of Applets and Views.
  3. Running the Siebel Web Client Migration Wizard.
  4. Reviewing Applet and View Migration.
  5. Running the Web Layout Wizard.
  6. Migrating Scripts Attached to Controls.
  7. Migrating Scripts Attached to Applets.
  8. Migrating Business Component, Business Service, and Application Scripts.
  9. Migrating Outbound COM Interfaces.
  10. Migrating Inbound COM Interfaces.
  11. Regenerating the Postmerge Utilities Log.
  12. Reviewing Customized Business Components.

Upgrade Custom Database Schema (upgphys)

  1. Run the Database Configuration Wizard to extract the storage control file from the target database 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.

  2. Remove EIM tables using the procedure described in Removing Interface Tables and Triggers. It is recommended that you remove EIM tables before synchronizing the Siebel logical and physical schema (Step 64) to ensure that the synchronization process does not fail when processing EIM tables.
  3. Run the Database Configuration Wizard to complete the development environment upgrade:
    • Choose the following settings:
      • Upgrade Options: Upgrade Custom Database Schema (upgphys)
      • Environment Type: Development
      • Storage Control File: Storage control file that you generated in Step 60.
    • 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.

      Launch the Siebel Upgrade Wizard. SQL commands are executed on the development environment database and a number of output files are generated.

  4. Transferring the Development Environment Upgrade Output Files to the z/OS Host.
  5. Synchronizing the Schema.
  6. Migrating Custom Business Component Configurations.
  7. About the Siebel Upgrade Log Files.
  8. 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.
  9. Manually Archiving Upgrade Log Files.
  10. Back up the upgraded database.
  11. Deleting Redundant Upgrade Files.

Initialize and Extract Developers' Local Databases

  1. Install the new release of Siebel Tools on developers' machines.
  2. Initialize and extract the local database on development machines. For more information about this task, see Developing and Deploying Siebel Business Applications.

Review the User Interface

  1. (Optional). Compile an SRF file to help review the UI. See Creating a New SRF File.
  2. If you customized style sheet or web template files in the previous release, you have to implement those customizations in the new release again, if desired.

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

  3. Perform the relevant tasks in the chapter of the Siebel Database Upgrade Guide that describes reviewing the Siebel user interface.
  4. The postmerge utilities do not convert certain types of flow-based applets to grid-based applets. For example, they do not convert custom form applets to grid-based applets. Convert remaining flow based applets as desired. For further information on editing applet layout, see Configuring Siebel Business Applications.

Postmerge Development Tasks

77 Perform the relevant tasks in the chapter of the Siebel Database Upgrade Guide that describes the Siebel postmerge development tasks.
  1. Resolve any business component and join conflicts.

Postupgrade Tasks for Database and File System

  1. Perform the applicable tasks in:
  2. Perform the tasks in Postupgrade Tasks for a Siebel Development Environment.
  3. 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.
  4. If you exported data from interface tables before the upgrade, review the database and import the data as desired.
  5. Upgrading to Siebel RC2 or AES Encryption. See the chapter of the Siebel Database Upgrade Guide that describes Siebel database and UI upgrade planning.

The development environment is now upgraded. The remaining sections deal with configuration and validation tasks.

Postupgrade Tasks for Applications Configuration

  1. If applicable, review the results of the Person and Organization merge. 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.
  2. Perform the applicable tasks in:
  3. Verify the function of interfaces in integrated applications.
  4. Activate and deploy workflows. To perform these tasks, see Siebel Business Process Framework: Workflow Guide.
  5. 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.
  6. 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.

Perform System Tests

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

Prepare for Transition to Production Test Environment

  1. Create a new SRF file. For information on creating an SRF file, see Developing and Deploying Siebel Business Applications.
  2. If you revised the repository after running upgphys, you must regenerate the repository definition files. See the chapter of the Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge for information on regenerating Siebel repository definition files.
    
Siebel Database Upgrade Guide for DB2 UDB for z/OS Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.