Siebel Database Upgrade Guide > How to Perform a Siebel Database Upgrade >

Process of Upgrading a Siebel Production Environment

Upgrades from: All Siebel releases.

Environments: Production environment.

Platforms: Windows and UNIX only. This topic does not apply to IBM z/OS.

To perform this process, you must be able to execute ODBC commands on the production database from within the production test environment. For more information, see About the Siebel Database Upgrade Process. If you cannot do this, contact Siebel Technical Support.

This process is part of a road map. See Road Map 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. It is divided into sections, each containing numbered steps. Complete the steps in the order shown.

CAUTION:  Do not use this topic to perform a production upgrade on IBM z/OS. Instead, see Siebel Database Upgrade Guide for DB2 UDB for z/OS.

Check SupportWeb

1. Check Siebel SupportWeb for recently published Technical Notes and Alerts regarding upgrades:
   • SupportWeb > Installation and Upgrade
   • SupportWeb > Technical Notes > Installation; Upgrade; Configuration-Dev Env; Configuration-General
   • SupportWeb > Siebel Alerts > Installation; Upgrade; Configuration Dev Env; Configuration-General
   • About Siebel Upgrade Planning Resources

Upgrade the Servers

Verify that you have identified all the maintenance releases, Fix Packs, and quick-fix patches required for the upgrade. These requirements are located on Siebel SupportWeb under Product Documentation > Maintenance Release Guides.

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.

2. Upgrade the Gateway Name Server, Siebel Servers, and Siebel Web Server Extension (SWSE).

   For information upgrading these Siebel Enterprise components, see Siebel Installation Guide for the operating system you are using.

3. Install the Siebel Database Server files on the Siebel Server you will use to perform the upgrade. You only need to install the database server files for the database type that you are upgrading.
4. Install the 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.

Upgrade Third-Party Software

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

7. If required, upgrade the RDBMS version. Refer to the vendor's documentation to perform the upgrade:
   • For information on supported RDBMS systems, see System Requirements and Supported Platforms on Siebel SupportWeb.
   • For information on how upgrading your RDBMS affects the upgrade process, see About Upgrading Your RDBMS in the Siebel Environment.

Pre-Upgrade Tasks for the Siebel Database

These steps apply to all database types.

8. Review guidelines for configuring the RDBMS. See the Siebel Installation Guide for the operating system you are using.
9. Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
10. Stop the Siebel Servers and the Siebel Gateway Name Server.
11. Close all database connections. The only open connection must be the account performing the upgrade.
12. Perform the tasks in Basic Database Preparations for a Siebel Upgrade.

Pre-Upgrade Tasks for IBM DB2

13. Perform the tasks in Preparing an IBM DB2 Database for a Siebel Upgrade.
14. Execute runstats on the Siebel database. This will improve upgrade performance.

Pre-Upgrade Tasks for Oracle

15. Perform the tasks in Preparing an Oracle Database for a Siebel Upgrade.
16. Run the Oracle Analyze command on the Siebel database. Highly fragmented indexes can cause the upgrade to fail.

Pre-Upgrade Tasks for Microsoft SQL Server

17. Perform the tasks in Preparing an Microsoft SQL Server Database for a Siebel Upgrade.
18. Run Microsoft SQL Server statistics. This will improve upgrade performance.

Pre-Upgrade Tasks for Application Data

19. Perform the tasks in Technical Note 521 on Siebel SupportWeb. Table 21 shows the applicability of the tasks in the Technical Note.

20. Perform the tasks in the Technical Notes and Alerts on Siebel SupportWeb shown in Table 22.

21. Perform the tasks in Preparing Siebel Application Data for Upgrade.

Pre-Upgrade Tasks for the UI

22. Copy application files to the environment:
    1. Custom SRF file.
    2. Reports files.
    3. Custom Web templates and style sheets. See Copying UI Files to a New Siebel Environment.

Upgrade the Siebel Database (upgrep)

You do not run the upgrep and upgphys portions of the upgrade in the production environment. Instead, the numbered steps in this topic implement the following process:

• Run the Database Configuration Wizard in the production test environment.
• In the Utilities, enter the information for the production environment instead of the production test environment. For example, you enter the ODBC connection for the production environment.

  This information configures the driver file to run against the production database rather than the production test database. It also configures the driver file to use the upgrade SQL files you generated for the production test upgrade.

• Run the Upgrade Wizard. The Upgrade Wizard uses the SQL files in the production test environment to upgrade the database in the production environment.

This approach has several advantages:

• You do not have to generate upgrade SQL files in the production environment, and then manually transfer the customizations to them from the production test environment.
• You do not lose any changes to the SQL files that were made by Siebel Upgrade Tuner in the production test environment.
• You do not have to run the Database Configuration Wizard in Prepare for Production mode again.
• With some exceptions, you do not have to perform database-related configuration tasks required by Release Notes or Alerts again.

If your network configuration prevents creating an ODBC connection to your production database from inside your production test environment, contact Siebel Technical Support for assistance in completing the production upgrade.

23. Verify you have a current backup of the production environment database.
24. On the Siebel Server you used to upgrade the production test environment, create an ODBC to connect to the production environment database.
25. Navigate to DBSRVR_ROOT\common (UNIX: DBSRVR_ROOT/common) and verify that the file sqlgen.usg exists.

    This file contains a record of when the SQL generator was run. When you run the Database Configuration Wizard, if this file exists, no SQL commands are generated.

    CAUTION:  If this file does not exist, do not run the Database Configuration Wizard. It will overwrite the SQL files used to upgrade your production test database. Contact Siebel Technical Support for guidance on proceeding with the upgrade.

    You do not have to run the Database Configuration Wizard in Prepare for Production Mode.

26. (Optional) Changing the Siebel Database Server Configuration Utilities Language.
27. Run the Database Configuration Wizard:
    • Preparing to Run the Siebel Database Configuration Wizard.
    • Running the Siebel Database Configuration Wizard Under Windows.
    • Running the Siebel Database Configuration Wizard Under UNIX.
    1. Choose the following settings when you run the utility:
       • Upgrade Options: Upgrade Siebel Database Schema (upgrep)
       • Environment Type: Production
    2. Enter the information for the production environment instead of the production test environment.
    3. Enter the name of the ODBC for connecting to the production database.
    4. When prompted whether you want to run the Siebel Upgrade Wizard, answer No and exit.

       This updates the master UCF file with the production environment configuration. When you run the Siebel Upgrade Wizard, the SQL commands will be executed on the production environment database.

28. If you have used the Upgrade Tuner to revise the SQL commands used in the production test environment, start the Upgrade Tuner, then click Save + Exit. See About Tuning Siebel Production Upgrade Files.

    This updates the master UCF file with basic Upgrade Tuner information. It does not change any SQL commands.

29. In the production test environment, verify that the SQL scripts for performing the upgrade were not overwritten. You can do this by checking the modification times. If the scripts were overwritten, do not continue. Instead, contact Siebel Technical Support.
30. Perform the production database upgrade. See Starting the Siebel Upgrade Wizard.

    The Siebel Upgrade Wizard uses the SQL commands generated for the production test environment to upgrade the production environment. If you used Upgrade Tuner to revise the SQL commands, these changes are included.

31. Review the upgrade logs and resolve errors:
    • Summarizing Siebel Log Files Using the Logparse Utility.
    • Reviewing Siebel Upgrade Log Files for Errors.
32. If the upgrade contains unacceptable errors, do the following:
    1. Restore the backup of the database.
    2. Correct the errors.
    3. Rerun the Siebel Upgrade Wizard.
33. Multilingual deployments: Perform the steps in Technical Note 447 on Oracle's Siebel SupportWeb to import language-specific repository strings and seed data into the upgrade repositories.

Upgrade Custom Database Schema (upgphys)

You upgrade the production database by using the SQL scripts in the production test environment. In the production test environment, you run the Database Configuration Wizard but enter environment information for the production database. Then you start the Siebel Upgrade Wizard in the production test environment. The Siebel Upgrade Wizard uses the production database environment information and the SQL in the production test environment, including any changes you have made, to upgrade the production database.

34. Verify you have a current backup of the production environment database.
35. On the Siebel Server you used to upgrade the production test environment, verify you have created an ODBC to connect to the production environment database.
36. Run the Database Configuration Wizard:
    • Preparing to Run the Siebel Database Configuration Wizard.
    • Running the Siebel Database Configuration Wizard Under Windows.
    • Running the Siebel Database Configuration Wizard Under UNIX.

      Choose the following settings:

    • Upgrade Options: Upgrade Custom Database Schema (upgphys)
    • Environment Type: Production
37. Run the Upgrade Wizard: Starting the Siebel Upgrade Wizard.
38. Review the upgrade logs and resolve errors:
    • Summarizing Siebel Log Files Using the Logparse Utility.
    • Reviewing Siebel Upgrade Log Files for Errors.
39. If the upgrade contains unacceptable errors, do the following:
    1. Restore the backup of the database.
    2. Correct the errors.
    3. Restart the Siebel Upgrade Wizard.
40. Manually Archiving Siebel Upgrade Log Files.
41. Installing New Siebel License Keys During an Upgrade.
42. Use the Siebel Application Deployment Manager to migrate administrative data such as LOVs and responsibilities from production test to production. See Going Live with Siebel Business Applications.
43. Back up the upgraded production environment database.

Postupgrade Tasks for Database and File System

44. Perform the tasks in Postupgrade Tasks for the Siebel Database and File System.
45. 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 for recommended parameter settings.
46. If you exported data from interface tables before the upgrade, review the database and import the data as desired.
47. Upgrade Planning for Siebel RC2 or AES Encryption.
48. Generate a Siebel Remote database template file. See Siebel Remote and Replication Manager Administration Guide.
49. (Oracle database 9i and later). Set Optimizer Mode to CBO. See Setting Oracle Database Configuration Parameters for a Siebel Upgrade.
50. Run database statistics.

NOTE:  The upgrade is complete. The remaining topics deal with configuration and validation tasks.

Postupgrade Tasks for Applications Configuration

51. If applicable, review the results of the Person and Organization merge. Make configuration changes as required. To determine applicability or obtain more information, see About the Siebel Party Model.
52. Perform the tasks in Postupgrade Tasks for Siebel Applications.
53. Verify the function of interfaces in integrated applications.
54. Activate and deploy workflows.
55. 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 EAI, see Overview: Siebel eBusiness Application Integration Volume I.
56. If you have used EIM to set up batch processing jobs, verify EIM is configured correctly. For information on EIM, see Siebel Enterprise Integration Manager Administration Guide.
57. If you customized the style sheet or Web template files in the previous release, reimplement those customizations in the new release as desired.

System Tests

58. Use available test data to perform unit testing. Validate the operation of the application in the following areas:
    • User interface
    • Data interfaces
    • Integrity of migrated data
    • Workflow function