4How to Perform a Siebel Database Upgrade

How to Perform a Siebel Database Upgrade

This chapter provides a roadmap for performing each type of upgrade to the current Siebel CRM release. Each roadmap lists the processes and tasks you must follow to complete the upgrade. Print the relevant roadmap and use it to guide you in carrying out the upgrade. This chapter includes the following topics:

• Roadmap for Performing a Siebel Database Upgrade

• Process of Planning a Siebel Database Upgrade

• Process of Upgrading a Siebel Development Environment

• Process of Upgrading a Production Test Environment

• Process of Tuning the Upgrade Performance

• Process of Upgrading a Siebel Production Environment

Roadmap for Performing a Siebel Database Upgrade

Upgrades: All upgrades.

Environments: All environments.

Use one of the following roadmaps to guide you through the steps for upgrading your Siebel database:

• Roadmap for Upgrading from Siebel 7.8.2, 8.0.x or 8.1.1.x

• Roadmap for Upgrading from Siebel 7.8.2, 8.0.x or 8.1.1.x

• Roadmap for Upgrading from Siebel 7.x, 8.0.x or 8.1.1.x Without a Development Environment

Each roadmap consists of a group of processes. Each process consists of a numbered list of tasks. After you complete the tasks in a process, go on to the next process in the roadmap. When you have completed all the processes in the roadmap, the upgrade is complete.

Depending on your installed release, you might not have to complete all the tasks in a process. Before starting a task, check the applicability information at the beginning of the task and verify the task applies to your upgrade.

Roadmap for Upgrading from Siebel 7.8.2, 8.0.x or 8.1.1.x

Note: This roadmap describes how to upgrade from one major release to another. For information on upgrading from Siebel 8.1.1.x to Siebel Innovation Pack 2016 or later, see Performing the Siebel Incremental Repository Merge.

If you are upgrading from Siebel CRM version 7.8.2 or higher to version 8.1. complete the processes in this roadmap in the order shown:

1. Process of Planning a Siebel Database Upgrade

2. Process of Upgrading a Siebel Development Environment

3. Process of Upgrading a Production Test Environment

4. Process of Tuning the Upgrade Performance

5. Process of Upgrading a Siebel Production Environment

For a description of the differences between production and development upgrades, see About Siebel Upgrade Environments.

Roadmap for Upgrading from Siebel 7.x, 8.0.x or 8.1.1.x Without a Development Environment

If you are upgrading from Siebel CRM Release 7.x, 8.0.x or 8.1.1.x, and you do not have a development environment, complete the processes in this roadmap in the order shown.

Upgrading without a development environment means the following are true:

• You are running an uncustomized, preconfigured version of Siebel Business Applications.

• You have not used Siebel Tools to create or modify any objects or logical schema definitions in the Siebel Repository.

• You have not modified the physical schema in the Siebel database.

If your upgrade meets these criteria, complete the following processes in the order shown:

1. Process of Planning a Siebel Database Upgrade.

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

3. Perform a production test upgrade. See Process of Upgrading a Production Test Environment.

4. Process of Tuning the Upgrade Performance.

5. Upgrade your production environment. See Process of Upgrading a Siebel Production Environment.

Process of Planning a Siebel Database Upgrade

Upgrades: All upgrades.

Environments: All environments.

This process is part of an upgrade roadmap. See Roadmap for Upgrading from Siebel 7.8.2, 8.0.x or 8.1.1.x and Roadmap for Upgrading from Siebel 7.x, 8.0.x or 8.1.1.x Without a Development Environment.

To plan the upgrade, read the following:

1. How the Siebel Database Upgrade Works

2. In the chapter in Siebel Database Upgrade Guide that describes how the Siebel database upgrade works, read topics about the following:

   • About the Siebel case insensitivity wizard

   • About the Siebel repository merge

   • About inheriting upgrade behavior in a Siebel upgrade

   • About the Siebel postmerge utilities

   • About the Siebel Incorporate Custom Layout upgrade option

   • About the Database Configuration Utilities

3. Planning a Siebel Database Upgrade

4. In the chapter in Siebel Database Upgrade Guide that describes Siebel database and UI upgrade planning, read topics about the following:

   • About Siebel upgrade planning resources

   • About best practices for doing your Siebel database upgrade

   • About Siebel user interface changes

   • About the Siebel Party Model

   • About migrating Siebel HTML attachments to base tables

   • Upgrade planning for multilingual Siebel deployments

   • Upgrade planning for Siebel RC2 or AES encryption

   • Upgrade planning for Siebel access control

5. The chapter in Siebel Database Upgrade Guide that describes application planning for a Siebel upgrade.

6. The appendix in Siebel Database Upgrade Guide that contains reference information on Siebel Marketing upgrades.

7. The appendix in Siebel Database Upgrade Guide that lists tables modified or seeded during a Siebel 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 subtopics, each containing a list of numbered steps. Complete each subtopic in the order shown.

Searching for Bulletins and Alerts on My Oracle Support

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

Upgrade Third-Party Software

If necessary, upgrade third-party software that is used by Oracle’s Siebel software. For example, you might have to upgrade the operating system software. Some database upgrades require newer versions of UNIX or Windows.

Upgrade the Servers

Verify that you have identified all the maintenance releases and Siebel Patchset releases for the upgrade.

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:

Install the Siebel CRM 8.1 Gateway Server and Siebel Servers.

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

1. Install the Siebel Database Configuration Utilities files on the Siebel Server you will use to perform the upgrade.

2. Install language packs for your currently deployed languages and any new languages.

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

If required, upgrade your version of DB2 for z/OS. Refer to the IBM documentation to perform the upgrade.

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. 7.5.3 upgrades only: Perform the task in Updating Table Space Group Names.

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

6. Prepare the storage control file to use in the upgrade. See Process of Preparing the Storage Layout of the Schema.

7. Perform the tasks in the following:

   • Basic Database Preparations for a Siebel Upgrade

   • The chapter in Siebel Database Upgrade Guide that describes basic database preparations for a Siebel upgrade.

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 task, see the chapter in Siebel Database Upgrade Guide that describes upgrading the Siebel database.

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.

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 must be the account that is performing the upgrade.

4. Install the new Siebel Tools on development workstations. Keep at least one copy of the previous version of Siebel Tools. You will require it to perform repository operations before the repository merge.

5. Activate the new Siebel Tools on development workstations. Keep at least one copy of the previous version of Siebel Tools. You will require it to perform repository operations before the repository merge.

6. Perform all remaining tasks with the new Siebel Tools, unless stated otherwise.

Upgrade Siebel Database Schema (upgrep)

1. (Optional) Change the Siebel Database Configuration Wizard language. For information on this topic, see the chapter in 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 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, Siebel 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. Restarting the Siebel Upgrade Wizard After Pauses.

   5. Preparing and Executing the Nonadditive 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. Dropping Partitioned EIM Tables.

   2. Process of Upgrading the Target Database.

   3. Performing the In-Place Target Database Upgrade.

5. Upgrade the repository and import seed data as described in 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 that you made previously (see Preparing Developers for the Upgrade).

   2. Correct the errors.

   3. Rerun the Database Configuration Wizard.

8. Activating New License Keys After an Upgrade.

9. Back up the upgraded database repository.

Prepare for Repository Merge

1. Perform the following tasks. For information on performing these tasks, see the chapter in Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge:

   • Migrate Siebel Repository objects to the standard user interface (UI).

   • Configure Siebel Repository objects to inherit upgrade behavior.

2. About Backing Up the New Customer Repository or Database Schema.

3. Execute the REORG utility on tables that receive a large number of inserts during the repository import process. For a list of the tables that must be reorganized at this point, see About Reorganizing Tables Before the Repository Merge.

4. Run database statistics on the Siebel repository tables. For further information on running database statistics, see Generating RUNSTATS Jobs. Running statistics on the Siebel repository tables improves merge performance.

   If upgrading from Siebel CRM versions 7. 7 or 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 Siebel CRM release, the S_SYM_STR and SYM_STR_INT tables are not populated until the merge is completed so you do not have 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.

   Note: If you are upgrading from Siebel CRM version 8.1.1.x fix pack (SIA repository) to Siebel Innovation Pack 2016 or later, refer to Performing the Incremental Repository Merge instead of this topic.

2. Review the Siebel Repository merge log files. For information on this task, see the chapter in 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. See About Backing Up the New Customer Repository or Database Schema.

   2. Correct the errors.

   3. Rerun the repository merge.

4. Run the Siebel postmerge Utilities. This task is not required if you are performing an incremental repository merge.

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

5. Perform the following tasks. For information on performing these tasks, see the chapter in Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge:

   • Delete unneeded Siebel repository files.

   • Generate Siebel Enterprise Integration Manager (EIM) temporary columns.

   • (Optional) Set label alignment for Siebel text fields.

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

7. Back up the Siebel database.

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

2. Run the Database Configuration Wizard to complete the development environment upgrade:

   • Choose the following settings:

     • Environment Type: Development.

     • Upgrade Options: Upgrade Custom Database Schema (upgphys).

     • Storage Control File: The storage control file that you generated in step 1.

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

3. Transferring the Development Environment Upgrade Output Files to the z/OS Host.

4. Synchronizing the Schema.

5. About the Siebel Upgrade Log Files.

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

7. Manually Archiving Upgrade Log Files.

8. Back up the upgraded database.

9. Deleting Redundant Upgrade Files.

Review the User Interface

1. Review Siebel Repository object property conflicts.

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

2. Carefully review the user interface in the new release by performing the tasks in the chapter in Siebel Database Upgrade Guide that describes reviewing the Siebel user interface.

3. If you customized style sheet or Web template files in the previous release, implement those customizations in the new release again and execute a full publish in Siebel Tools to compile the Siebel Runtime Repository data.

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

1. Perform the following tasks. For information on these tasks, see the chapter in Siebel Database Upgrade Guide that describes the Siebel postmerge development tasks:

   • Review objects deleted from the Siebel Repository

   • Review obsolete objects in the Siebel Repository

   • Upgrade to the Siebel symbolic string model

   • Update Siebel Enterprise Application Integration (EAI)

2. Resolve any business component and join conflicts.

Postupgrade Tasks for Database and File System

1. Perform the applicable 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.

Note: 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 about the Siebel Party Model in the chapter in Siebel Database Upgrade Guide that describes Siebel database and UI upgrade planning.

2. Perform the tasks in:

   • Postupgrade Tasks for Siebel Business Applications

   • The chapter in Siebel Database Upgrade Guide that describes the postupgrade tasks for Siebel Business Applications

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

If you revised the repository after running upgphys, you must regenerate the repository definition files. For information, see Regenerating the Siebel Repository Definition Files.

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

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

Upgrade Third-Party Software

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 UNIX or Windows.

Upgrade the Servers

Verify you have identified all the maintenance releases and Siebel Patchset releases for the upgrade.

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 Server and Siebel Servers.

   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

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.

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 Process of Preparing the Storage Layout of the Schema.

5. Perform the tasks in:

   • Basic Database Preparations for a Siebel Upgrade

   • The chapter in Siebel Database Upgrade Guide that describes the basic database preparations for a Siebel upgrade

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

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:

   • Reports files

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

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. Dropping Partitioned EIM Tables.

   3. Creating and Loading Siebel Log Tables

   4. Applying Additive Upgrade Changes to the Target Database.

   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. Activating New License Keys After an Upgrade.

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

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:

   • Postupgrade Tasks for Siebel Business Applications

   • The chapter in Siebel Database Upgrade Guide that describes the postupgrade tasks for Siebel Business Applications

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, implement those customizations in the new release again and execute a full publish in Siebel Tools to compile the Siebel Runtime Repository data.

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

Perform System Tests

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

Process of Tuning the Upgrade Performance

Upgrades: All upgrades.

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

This process is optional.

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

Caution: You are required to contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance with tuning your upgrade scripts. If you do not, you might invalidate your support agreement.

Use this process to run test upgrades in the production test environment so you can tune upgrade performance. Improving upgrade performance reduces downtime when you perform the production environment upgrade. The steps in this process cover standard performance tuning. For help with this process and to implement more advanced tuning, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance.

You can also use this process to test the additive schema changes feature to verify that it does not adversely affect application functionality. The additive schema changes feature allows you to perform part of the upgrade on the production database without taking it offline. This reduces the downtime required to upgrade the production database.

Perform this process in the production test environment. Do not perform this process in the production environment.

Review the following upgrade planning and performance tuning resources before performing this process:

• 478308.1 (Article ID) on My Oracle Support. This document was formerly published as Siebel Technical Note 616. This document describes strategies for minimizing production environment downtime during an upgrade. The steps outlined in this topic are intended primarily for use with the baseline best practices described in Technical Note 616.

• Tuning the Siebel Production Upgrade Scripts This chapter provides information on how you can improve the performance of the production environment upgrade by tuning the production upgrade scripts in a production test environment.

Set Up the Target Database

1. Back up and remove the upgraded production test database.

2. In the production test environment, install a recent backup of your production database.

   This database has not been upgraded and is called the target database. You use it to perform test upgrades as part of tuning upgrade performance.

3. Define an ODBC connection to the target database.

4. Verify that the target database is configured for optimum upgrade performance. Review the relevant topics in the following:

   • Basic Database Preparations for a Siebel Upgrade

   • The chapter in Siebel Database Upgrade Guide that describes the basic database preparations for a Siebel upgrade

5. (Optional) Run statistics on the target database if the catalog statistics require updating.

6. Perform the relevant tasks in the chapter in Siebel Database Upgrade Guide that describes how to prepare Siebel Business Applications data for upgrade.

Upgrade the Target Database Schema (upgrep + upgphys)

1. Using the upgrade files you generated during the production test upgrade, upgrade the target database by performing the following tasks:

2. Dropping Partitioned EIM Tables.

3. Applying Additive Upgrade Changes to the Target Database.

4. Performing the In-Place Target Database Upgrade.

5. Upgrade the repository and import seed data. See Upgrading the Repository and Importing Seed Data. Specify the storage control file you extracted when you performed the production test upgrade (see Upgrade the Siebel Database Schema (upgrep + upgphys)).

6. Activating New License Keys After an Upgrade.

7. Note the time required to upgrade the database.

8. Review the upgrade logs for errors. See About the Siebel Upgrade Log Files.

9. If the upgrade contains errors that prevented completion or adversely affected performance, correct the errors and rerun the upgrade.

10. Manually Archiving Upgrade Log Files.

Tune the Upgrade Files

1. Evaluate upgrade performance, particularly the time required to complete the upgrade.

2. Do one of the following:

   • If the time required to complete the upgrade is acceptable, no further tuning is required. Perform the steps in Process of Upgrading a Siebel Production Environment.

   • If the time required to complete the upgrade is too long, perform the remaining steps in this subtopic to continue tuning upgrade performance.

   • If the time required to complete the upgrade is too long and you cannot tune further, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance in applying advanced tuning.

3. Carefully review target database and database server configuration. Adjust as required to further improve upgrade performance.

4. Tune the upgrade files:

   • Optimizing Unload and Load Job Performance.

   • Adding the Statistics Clause to Load Cards.

5. Copy the tuned upgrade scripts to a safe location for use in the production upgrade.

Restore the Target Database

Perform these steps if you have made changes to the upgrade environment or to the upgrade files and want to run the upgrade again to verify performance improvement.

1. In the production test environment, restore the target database from backup.

   This returns the target database to its nonupgraded state so that you can perform another test upgrade.

2. In the production test environment, perform another test upgrade and evaluate upgrade performance.

3. Repeat the tuning process and perform test upgrades until upgrade performance is acceptable.

4. When you have completed tuning upgrade performance in the production test environment, delete and remove the target database.

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

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 UNIX or Windows.

Upgrade the Servers

Verify you have identified all the maintenance releases and Siebel Patchset releases for the upgrade.

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.

1. Install the Siebel CRM 8.1 Gateway Name Server and Siebel Servers.

   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

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.

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. Verify there are no open database connections.

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

6. Prepare the storage control file to use in the upgrade. See Process of Preparing the Storage Layout of the Schema.

7. Perform the applicable tasks in the following:

   • Basic Database Preparations for a Siebel Upgrade

   • The chapter in Siebel Database Upgrade Guide that describes the basic database preparations for a Siebel upgrade

Preupgrade Tasks for Application Data

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 Environment Upgrade

1. Review the information in Requirements for Upgrading the Production Environment.

2. Copy application files to the environment:

   1. Reports files.

   2. Custom 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.

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

4. Preparing for a No-Development-Environment Siebel Upgrade.

   If you do not have a development environment, see Preparing for a Siebel Upgrade Without a Development Environment 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 Siebel Release Notes on My Oracle Support or by 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.

1. Verify you have a current backup of the production environment database.

2. On the Siebel Server you used to upgrade the production test environment, create an ODBC to connect to the production environment database.

3. 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 might have 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.

4. Upgrade the target database using the tuned upgrade files, which now contain production environment information, by performing the following tasks:

   1. Dropping Partitioned EIM Tables.

   2. Applying Additive Upgrade Changes to the Target Database.

   3. Renaming the Production Environment Repository.

   4. Performing the In-Place Target Database Upgrade.

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

6. Upgrade the repository and import seed data. See Upgrading the Repository and Importing Seed Data.

7. Activating New License Keys After an Upgrade.

8. About the Siebel Upgrade Log Files.

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

10. Manually Archiving Upgrade Log Files.

11. Back up the upgraded production database.

12. Deleting Redundant Upgrade Files.

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. Generate database statistics for new or rebuilt tables and indexes. Determine whether or not any tables must be reorganized by running RUNSTATS with the Report Only option specified. For more information about running statistics, see Generating RUNSTATS Jobs.

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

Postupgrade Tasks for Applications Configuration

1. Review the results of the Person and Organization merge, if applicable. Make configuration changes as required. For further information, see the topic about the Siebel Party Model in the chapter in Siebel Database Upgrade Guide that describes Siebel database and UI upgrade planning.

2. Perform the tasks in the following:

   • Postupgrade Tasks for Siebel Business Applications

   • The chapter in Siebel Database Upgrade Guide that describes the postupgrade tasks for Siebel Business 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, implement those customizations in the new release again and execute a full publish in Siebel Tools to compile the Siebel Runtime Repository data.

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

Deploy to Users

1. Upgrade your Siebel Mobile and Developer Web Clients. See Siebel Installation Guide for the operating system you are using for further information.

2. 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. For information on this task, see Siebel System Administration Guide.

3. Use Siebel Anywhere to create distribution kits for deployment. See Siebel Anywhere Administration Guide.

4. Generate a Siebel Remote database template. See Siebel Remote and Replication Manager Administration Guide.

5. Set up database extraction for Siebel Mobile Web Clients. See Siebel Remote and Replication Manager Administration Guide.