Bookshelf Home | Contents | Index | PDF     

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

Process of Upgrading a Production Test Environment

Upgrades: All upgrades.

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

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

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

NOTE:  The production test environment must replicate the production environment exactly.

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

Searching for Bulletins and Alerts on My Oracle Support

  1. Check My Oracle Support for recently published bulletins and alerts regarding the upgrade.

Upgrade Third-Party Software

  1. Upgrade third-party software that is used by Oracle's Siebel software if required. For example, you might have to upgrade the 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 for the upgrade. These requirements are documented in 880452.1 (Article ID) Siebel Maintenance Release Guide on My Oracle Support.

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

To perform the following steps, see Siebel Installation Guide for the operating system you are using and Implementing Siebel Business Applications on DB2 for z/OS. Do the following:

  1. Install the Siebel CRM 8.1 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. For information on this task, see Siebel System Administration Guide.

Upgrade the RDBMS

  1. If required, upgrade your version of DB2 for z/OS and DB2 Connect middleware. You might also have to upgrade any DB2 clients that connect to the Siebel database. Refer to the IBM documentation to perform the DB2 for z/OS and DB2 Connect upgrades. To upgrade to Siebel CRM version 8.1, your RDBMS must be IBM DB2 UDB for z/OS Version 8.

Preupgrade Tasks for the Siebel Database

  1. Review guidelines for configuring DB2 for z/OS. For information, 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. Remove customized database triggers.

    The Siebel upgrade process is not designed to support custom database triggers. If you have created customized triggers for the Siebel schema to be upgraded, you must remove them before starting the Siebel upgrade process. You can re-create these objects once the Siebel upgrade completes successfully.

  4. Prepare the storage control file to use in the upgrade. See Preparing the Storage Layout of the Schema.
  5. Perform the tasks in:
  6. Before starting the production test upgrade, ensure that:
    • Siebel database transactional tables with clustering indexes are organized in cluster sequence.
    • Generate database statistics for your Siebel database transactional tables, if required.

Preupgrade Tasks for Application Data

  1. Perform the tasks in the chapter in 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 Test Environment Upgrade

  1. Review the information in Requirements for Upgrading the Production Environment.
  2. For instructions on how to set up the Siebel database and Siebel Servers in the production test environment, refer to 477772.1 (Article ID) on My Oracle Support. This document was formerly published as Siebel Technical Note 586.
  3. Stop the Siebel Servers.
  4. Close all database connections. The only database connection must be the account performing the upgrade.

    Disconnect the Siebel Server from the development environment database and connect it to the production test environment database.

  5. Copy application files to the environment:
    • Custom SRF file
    • Reports files
    • Custom Web templates and style sheets

      See the topic on copying UI files to a new Siebel environment in the chapter in Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge.

  6. About Moving the Customized Repository and Schema Definition Files.

    If you revised repository objects or schema definitions after performing your development environment upgrade, regenerate the schema.ddl and custrep.dat files before transferring them to the production test environment. For information, see Regenerating the Siebel Repository Definition Files.

  7. Preparing for a Siebel Upgrade Without a Development Environment.

    If you do not have a development environment, perform this task.

  8. Verify the production test database is either a copy of the current production database or has the same topology and a similar amount of data. This is important for effective performance testing of the upgrade scripts.
  9. Back up the production test environment database. To do upgrade tuning, you will restore this database and perform test upgrades on it.

Prepare for Production

  1. (Optional) Change the Siebel Database Configuration utilities language. For information on this topic, see the chapter in Siebel Database Upgrade Guide that describes how to upgrade the Siebel database.
  2. (7.5.3 Upgrades only) Run the Database Configuration Wizard as described in About Running the Database Configuration Wizard on Windows or About Running the Database Configuration Wizard Under UNIX. Do the following:
    1. Specify the following options:
      • Upgrade Options: Prepare for Production Upgrade
      • Environment Type: Production
    2. Launch the Siebel Upgrade Wizard.

Upgrade the Siebel Database Schema (upgrep + upgphys)

  1. 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 Upgrade Environment and Creating the Staging Database.
    5. Removing Interface Tables and Triggers.
  2. Generate the upgrade files by performing the following tasks:

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

    1. Required 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. Applying the Additive Schema Changes to the Production Staging Database.
    5. Restarting the Siebel Upgrade Wizard After Pauses.
    6. Preparing and Executing the Nonadditive Schema and JCL Files on the z/OS Host.
    7. Restarting the Siebel Upgrade Wizard After Pauses.
    8. Processing the Index Schema File.
    9. Building JCL Templates for the Target Database.
  3. Upgrade the target database by performing the following tasks:
    1. Read Process of Upgrading the Target Database.
    2. Creating and Loading Siebel Log Tables.
    3. Applying Additive Upgrade Changes to the Target Database.
    4. Generate statistics for tables and indexes that were created or rebuild when additive schema changes were applied to the database. You might also have to reorganize these tables and indexes. For further information on generating database statistics, see Generating RUNSTATS Jobs.
    5. Renaming the Production Environment Repository.
    6. Performing the In-Place Target Database Upgrade.
  4. 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. You must specify the name 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.

  5. Upgrade the repository and import seed data. See Upgrading the Repository and Importing Seed Data.
  6. Performing Intersection Table Maintenance.
  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.

Postupgrade Tasks for Database and File System

  1. Perform the relevant tasks in Postupgrade Tasks for Siebel Database and File System.
  2. Perform the following tasks. For information on these tasks, see the chapter in Siebel Database Upgrade Guide that describes postupgrade tasks for the Siebel database and file system:
    • Check for inactivated EIM table columns in the Siebel database
    • Validate dock objects and rule definitions in the Siebel database
  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. Upgrade unencrypted data and data that was encrypted using the standard encryptor to RC2 or AES encryption. For information on this task, see the chapter in Siebel Database Upgrade Guide that describes Siebel database and UI upgrade planning.
  6. Ensure Siebel database transactional tables with clustering indexes are organized in cluster sequence, and check whether or not you have to run the REORG utility on new tables.
  7. Generate database statistics for new or rebuilt tables and indexes using the RUNSTATS utility. For more information about running statistics, see Generating RUNSTATS Jobs.

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

Postupgrade Tasks for Siebel Application Configuration

  1. Perform the tasks in the following to prepare for system testing:
  2. Verify the function of interfaces in integrated applications.
  3. Activate and deploy workflows. To perform these tasks, see Siebel Business Process Framework: Workflow Guide.
  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 using 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 using EIM, see Siebel Enterprise Integration Manager Administration Guide.
  6. If you customized style sheet or web template files in the previous release, you must implement those customizations in the new release again, if desired.

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

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
    
Siebel Database Upgrade Guide for DB2 for z/OS Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.