Upgrade Guide for DB2 UDB for z/OS > How to Perform the 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 the 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 should replicate the production environment exactly.

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

Upgrade Third-Party Software

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

     For further information, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.

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.

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

2. Install the Siebel 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.

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.
5. If you have customized the configuration of Enterprise components, such as Siebel Servers, you must manually enter the customizations in the upgraded environment. See Going Live with Siebel Business Applications.

NOTE:  You do not install a new Siebel database as part of upgrading the Siebel Enterprise.

Upgrade the RDBMS

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

Identify and Resolve Duplicate Row IDs

7. 6.2.1 upgrades only: Identifying and Resolving Duplicate Row IDs.

   After you install the Siebel Database Server 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

8. 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.
9. Review 477519.1 (Article ID) on My Oracle Support. This document was previously published as Siebel 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.
10. Review guidelines for configuring the RDBMS. See Implementing Siebel Business Applications on DB2 UDB for z/OS.
11. Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
12. Stop the Siebel Server and the Siebel Gateway Name Server.
13. Verify there are no open database connections.
14. Perform the tasks in Basic Database Preparations.

Preupgrade Tasks for a Production Environment Upgrade

15. Perform the tasks in Preparing a Production Environment for Upgrade.

    You must perform the task Transferring the Customized Repository and Schema Definition Files.

Preupgrade Tasks for Application Data

16. Perform the relevant tasks in Preparing 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.

Prepare the Siebel Database for Upgrade

17. If you revised repository objects or schema definitions after performing your development environment upgrade, regenerate the schema.ddl and custrep.dat files and import them to the production test environment. See Regenerating the Repository Definition Files and Transferring the Customized Repository and Schema Definition Files.
18. 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.
19. Verify you have a current backup of the production test environment database. To do upgrade tuning, you will restore this database and perform test-upgrades on it.
20. On the Siebel Server you used to upgrade the development environment database, create an ODBC to connect to the production test environment database.
21. Disconnect the Siebel Server from the development environment database and connect it to the production test environment database.
22. 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.

      Choose the following settings:

    • Upgrade Options: Prepare for Production
    • Environment Type: Production

Upgrade the Siebel Database Schema (upgrep + upgphys)

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

      Enter configuration information for the production test environment. The master UCF file is updated with the production test environment configuration.

24. Review the following topic and perform the procedure if applicable: Migrating Address Data from Custom Extension Columns.
25. Enter Yes on the Database Server Configuration utility screen to launch the Siebel Upgrade Wizard. SQL commands are executed on the production test environment database until the Upgrade Wizard stops at the First Pause.
26. Preparing the z/OS Host Environment.
27. Resuming the Siebel Upgrade Wizard After the First Pause.
28. Transferring Control Cards and Schema DDL Files to the z/OS Host.
29. Preparing the Schema and JCL Files on the z/OS Host.
30. Installing Stored Procedures on the z/OS Host.
31. Preparing Siebel-Scheduled Jobs on the z/OS Host.
32. Optimizing the Target Job Stream, Part 1.
33. Optimizing Old-Schema Index Rebuild Jobstreams.
34. Loading Log Tables on the Source Database.
35. Loading Log Tables on the Target Database.
36. Executing the Upgrade on the z/OS Host (Phase 1 of 2).
37. Resuming the Siebel Upgrade Wizard on the Midtier After the Second Pause.
38. Transferring the Index Schema to the z/OS Host.
39. Preparing Siebel-Scheduled JCL.
40. Optimizing the Target Job Stream, Part 2.
41. Executing the Upgrade on the z/OS Host (Phase 2 of 2).
42. Performing Intersection Table Maintenance.
43. Resuming the Siebel Upgrade Wizard on the Midtier After the Third Pause.
44. Reviewing Upgrade Log Files for Errors.
45. 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.
46. Manually Archiving Upgrade Log Files.
47. Installing New License Keys After Upgrade.
48. Back up the upgraded database.
49. Deleting Redundant Upgrade Files.

Postupgrade Tasks for Environment Setup

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

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

Postupgrade Tasks for Configuration

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

Configure for Globalization

58. Upgrading to the Symbolic String Model.
59. Setting Up Your Environment to Support Global Time Zone.

Deploy Workflows

Activate and deploy workflows. To perform these tasks, see Siebel Business Process Designer Administration Guide.

60. Upgrading Seeded Workflows.
61. Upgrading Inbound Workflows.

Verify Application Integration

62. 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.
63. Updating Enterprise Application Integration (EAI) After Upgrade.

Postupgrade Tasks for Application Administration

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

Perform System Tests

68. Thoroughly test all applications.