Siebel Database Upgrade Guide for DB2 for z/OS > How to Perform a Siebel Database Upgrade >
Process of Upgrading a Siebel Production Environment
Upgrades: All upgrades.
Environments: Production environment only. Does not apply to production test environment.
This process is part of a roadmap. See Roadmap for Performing a Siebel Database Upgrade.
This topic lists the tasks required to transition your production test environment to production. Print this topic and use it as a checklist for doing the upgrade.
The topic is divided into 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 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.
- 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.
- Install the Siebel Database Configuration Utilities files on the Siebel Server you will use to perform the upgrade.
- Install language packs for your currently deployed languages and any new languages.
- 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. 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
- Review guidelines for configuring DB2 for z/OS. See Implementing Siebel Business Applications on DB2 for z/OS.
- Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
- Stop the Siebel Servers.
- Verify there are no open database connections.
- 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.
- Prepare the storage control file to use in the upgrade. See Preparing the Storage Layout of the Schema.
- Perform the applicable tasks in the following:
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
- Review the information in Requirements for Upgrading the Production Environment.
- 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.
- About Moving the Customized Repository and Schema Definition Files.
- 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.
- Verify you have a current backup of the production environment database.
- On the Siebel Server you used to upgrade the production test environment, create an ODBC to connect to the production environment database.
- 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:
- Upgrade the target database using the tuned upgrade files, which now contain production environment information, by performing the following tasks:
- Creating and Loading Siebel Log Tables.
- Applying Additive Upgrade Changes to the Target Database.
- Renaming the Production Environment Repository.
- Performing the In-Place Target Database Upgrade.
- Extract the storage control file from the target database using the Database Configuration Wizard as follows:
- Upgrade the repository and import seed data. See Upgrading the Repository and Importing Seed Data.
- Performing Intersection Table Maintenance.
- About the Siebel Upgrade Log Files.
- If the upgrade contains unacceptable errors, do the following:
- Restore the backup of the database.
- Correct the errors.
- Rerun the Database Configuration Wizard.
- Manually Archiving Upgrade Log Files.
- Back up the upgraded production database.
- Deleting Redundant Upgrade Files.
Postupgrade Tasks for Database and File System
- Perform the relevant tasks in Postupgrade Tasks for Siebel Database and File System.
- 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
- 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.
- If you exported data from interface tables before the upgrade, review the database and import the data as desired.
- 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.
- 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
- 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.
- Perform the tasks in the following:
- Activate and deploy workflows. To perform these tasks, see Siebel Business Process Framework: Workflow Guide.
- 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.
- 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.
- If you customized style sheet or web template files in the previous release, you have to implement those customizations again in the new release, if desired.
Perform System Tests
- 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
- Upgrade your Siebel Mobile and Developer Web Clients. See Siebel Installation Guide for the operating system you are using for further information.
- 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.
- Use Siebel Anywhere to create distribution kits for deployment. See Siebel Anywhere Administration Guide.
- Generate a Siebel Remote database template. See Siebel Remote and Replication Manager Administration Guide.
- Set up database extraction for Siebel Mobile Web Clients. See Siebel Remote and Replication Manager Administration Guide.