Siebel Database Upgrade Guide > How to Perform a Siebel Database Upgrade >
Process of Upgrading a Siebel Production Environment
Upgrades from: All Supported 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 Technical Support.
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. 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.
Search for Bulletins and Alerts on OracleMetalink 3
- Check OracleMetalink 3 for recently published Bulletins and Alerts regarding the upgrade. For more information, see About Siebel Upgrade Planning Resources.
Upgrade the Servers
Verify you have identified all the maintenance releases, Fix Packs, and quick-fix patches required for the upgrade. These requirements are located in the applicable Siebel Maintenance Release Guide on OracleMetalink 3.
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.
- 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.
- 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.
- Install the 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 can run a script to migrate configuration parameters to the upgraded Siebel Enterprise. See Going Live with Siebel Business Applications.
Upgrade Third-Party Software
- 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.
Apply Additive Schema Changes
These steps are optional. Do not perform these steps unless you have thoroughly tested the additive schema changes feature in the production test environment and have verified that it will not adversely affect your applications.
Perform these steps on the production database. You do not need to take the production database offline. You can perform these steps anytime prior to running the production upgrep.
After applying additive schema changes there is no need to run database statistics. The schema changes do not affect the performance of your release prior to the upgrade.
- Review About Siebel Additive Schema Changes Mode.
- Verify you have a recent backup of the production database and that you are logging transactions.
If you encounter problems applying additive schema changes, you might need to restore the production database.
- (Optional) Changing the Siebel Database Configuration Utilities Language.
- In the production environment, start the Database Configuration Wizard:
- Choose Apply Additive Schema Changes mode.
The Apply Additive Schema Changes mode identifies changes that can be made to the production database without taking it offline.
Windows. You will not be prompted whether you want to run the Upgrade Wizard. Instead, the Upgrade Wizard starts automatically, and creates the
schema.additive.sql script. The Upgrade Wizard does not run the script against the production database.
- UNIX. Run the Siebel Upgrade Wizard.
See Starting the Siebel Upgrade Wizard.
master_additive_gen.ucf as the input file.
The Upgrade Wizard generates the
schema.additive.sql script. It does not run the script against the production database.
- Run the SQL script against the production database.
See Applying Siebel Additive Schema Changes.
- Thoroughly review the operation of all applications. Verify that applying additive schema changes has not adversely affected applications function.
- If applying additive schema changes adversely affects the operation of the application, do the following:
- Contact Oracle Global Support for help in diagnosing and correcting the problem.
- If required, restore the production database from backup.
Upgrade the RDBMS
- If required, upgrade the RDBMS version. Refer to the vendor's documentation to perform the upgrade:
Pre-Upgrade Tasks for the Siebel Database
These steps apply to all database types.
- Review guidelines for configuring the RDBMS. See the Siebel Installation Guide for the operating system you are using.
- Verify that the Workflow Monitor and Workflow action agents have processed all pending requests.
- Stop the Siebel Servers and the Siebel Gateway Name Server.
- Verify that the Siebel Gateway Name Server is running.
- Stop all other Siebel Servers.
- Close all database connections. The only open connection must be the account performing the upgrade.
- Perform the tasks in Basic Database Preparations for a Siebel Upgrade.
Pre-Upgrade Tasks for IBM DB2
- Perform the tasks in Preparing an IBM DB2 Database for a Siebel Upgrade.
- Make sure that runstats is current in your environment and that tables with clustering indexes are not out of cluster. Reorganize any tables that are out of cluster in advance of the upgrade if possible.
Pre-Upgrade Tasks for Oracle Database
- Perform the tasks in Preparing an Oracle Database for a Siebel Upgrade.
- 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
- Perform the tasks in Preparing a Microsoft SQL Server Database for a Siebel Upgrade.
- Run Microsoft SQL Server statistics. This will improve upgrade performance.
Pre-Upgrade Tasks for Application Data
- Perform the tasks in Bulletin 477519.1 (Doc ID) on OracleMetalink 3. This document was previously published as Siebel Technical Note 521. The following table shows the applicability of the tasks in the Bulletin.
Location and amendment of S_VIEW_WTMPL_IT.ITEM_NUM records
Development, production test, production
Update multi-value group (MVG) and association list applets
Update unnamed controls in applet web template items
- Perform the tasks in Preparing Siebel Application Data for Upgrade.
Pre-Upgrade Tasks for the UI
- Copy application files to the environment:
Upgrade the Siebel Database (upgrep and upgphys)
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:
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 again the database-related configuration tasks required by Siebel Release Notes on OracleMetaLink 3 or Alerts on OracleMetalink 3.
If your network configuration prevents creating an ODBC connection to your production database from inside your production test environment, contact Oracle Global Customer Support for assistance in completing the production upgrade.
- 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.
- 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 Oracle Global Customer Support for guidance on proceeding with the upgrade.
You do not have to run the Database Configuration Wizard in Prepare for Production Mode.
- (Optional) Changing the Siebel Database Configuration Utilities Language.
- Run the Database Configuration Wizard:
- Choose the following settings when you run the utility:
- Upgrade Options: Upgrade Siebel Database Schema (upgrep + upgphys)
- Environment Type: Production
- Enter the information for the production environment instead of the production test environment.
- Enter the name of the ODBC for connecting to the production database.
- 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.
- 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 your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.
- 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.
- Review the upgrade logs and resolve errors:
- If the upgrade contains unacceptable errors, do the following:
- Restore the backup of the database.
- Correct the errors.
- Rerun the Siebel Upgrade Wizard.
- Manually Archiving Siebel Upgrade Log Files.
- Installing New Siebel License Keys During an Upgrade.
- 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.
- Back up the upgraded production environment database.
Postupgrade Tasks for Database and File System
- Perform the tasks in Postupgrade Tasks for the Siebel Database and File System.
- 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.
- If you exported data from interface tables before the upgrade, review the database and import the data as desired.
- Upgrade Planning for Siebel RC2 or AES Encryption.
- Generate a Siebel Remote database template file. See Siebel Remote and Replication Manager Administration Guide.
- Run database statistics.
NOTE: The upgrade is complete. The remaining topics deal with configuration and validation tasks.
Postupgrade Tasks for Applications Configuration
- 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.
- Perform the tasks in Postupgrade Tasks for Siebel Applications.
- Verify the function of interfaces in integrated applications.
- Activate and deploy workflows.
- 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 Enterprise Application Integration.
- 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.
- If you customized the style sheet or Web template files in the previous release, reimplement those customizations in the new release as desired.
- 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