Siebel Database Upgrade Guide > Overview of Performing a Siebel Database Upgrade >
Process of Upgrading a Siebel 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 environment. For more information, see About the Siebel Database Configuration Utilities. For help executing ODBC commands within the production test environment, create a service request (SR) on My Oracle Support. NOTE: Links to other topics in this guide are provided throughout this chapter. These links are meant to provide additional information that cannot be provided in these brief overviews. You must, however, perform the upgrade in the proper order. For information on general planning, see this chapter as well as Siebel Database Upgrade Planning and Application Planning for a Siebel Upgrade. To begin the process of upgrading your Siebel database, see Preparing for Siebel Database Upgrade then refer to each subsequent chapter.
This topic lists the tasks required to transition your production test environment to production. Print this topic and use it as a checklist when doing the upgrade. Complete the steps in the order shown. NOTE: If you are performing a production environment upgrade on IBM z/OS, then see Siebel Database Upgrade Guide for DB2 for z/OS.
Search for Articles on My Oracle Support
Upgrade the Servers
Verify that you have identified all of the Siebel CRM releases that are required for the upgrade. Along with the current release, Siebel Innovation Pack 2014, also install the latest Siebel Patchset release. For more information on server upgrade and installation, see the Siebel Installation Guide for the operating system you are using. See also the Certifications tab on My Oracle Support. 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 Siebel 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, then you can run a script to migrate configuration parameters to the upgraded Siebel Enterprise. (Do not perform this step for a migration installation, which is described in the Siebel Installation Guide for the operating system you are using.)
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 might need to upgrade the following software:
- Operating system software. Some database upgrades require newer versions of AIX or Windows.
Apply Additive Schema Changes
These steps are optional. Perform these steps only after 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 that you have a recent backup of the production database and that you are logging transactions.
If you encounter problems applying additive schema changes, then 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.
Specify 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 you are applying additive schema changes adversely affects the operation of the application, then 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:
Perform Preupgrade 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.
- Verify that the Siebel Gateway Name Server is still 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 Preparing for Siebel Database Upgrade.
Perform Preupgrade Tasks for IBM DB2
- Perform the tasks in Preparing an IBM DB2 Database for a Siebel Upgrade.
- Make sure that all transactional tables with clustering indexes are at least 90% clustered and stats are current.
NOTE: You might be required to perform runstats on a small number of transactional tables and indexes following a successful upgrade. All Siebel Enterprise Integration Manager tables will have been replaced and might need statistics gathered.
Perform Preupgrade 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.
Perform Preupgrade 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.
Perform Preupgrade Tasks for Application Data
- Perform the tasks in 477519.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 521. The following table shows the applicability of the tasks in the article.
|
|
Location and amendment of S_VIEW_WTMPL_IT.ITEM_NUM records |
Development, production test, production |
Update multi-value group (MVG) and association list applets |
Development only |
Update unnamed controls in applet Web template items |
Development only |
- Perform the tasks in Preparing Siebel Application Data for Upgrade.
Perform Preupgrade Tasks for the UI
- Copy application files to the environment:
- Custom SRF file.
- Reports files.
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 My Oracle Support or Articles on My Oracle Support.
If your network configuration prevents creating an ODBC connection to your production database from inside your production test environment, then contact Oracle Global Customer Support for assistance in completing the production upgrade.
- Verify that 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, then no SQL commands are generated.
CAUTION: If this file does not exist, then do not run the Database Configuration Wizard. The Database Configuration Wizard 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 and 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, then 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, then these changes are included.
- Review the upgrade logs and resolve errors: Reviewing Siebel Upgrade Log Files for Errors.
- If the upgrade contains unacceptable errors, then do the following:
- Restore the backup of the database.
- Correct the errors.
- Rerun the Siebel Upgrade Wizard.
- Manually Archiving Siebel Upgrade Log Files.
- Use the Siebel Application Deployment Manager to migrate administrative data such as LOVs and responsibilities from production test to production.
- Back up the upgraded production environment database.
Perform Postupgrade Tasks for Database and File System
- Perform the tasks in Postupgrade Tasks for 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 for recommended parameter settings.
- If you exported data from interface tables before the upgrade, then review the database and import the data as desired.
- 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.
Perform Postupgrade Tasks for Applications Configuration
- If applicable, review the results of the Person and Organization merge. Make configuration changes as required.
- Perform the tasks in Postupgrade Tasks for Siebel Business 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 Enterprise Application Integration, then verify that the integrations are configured correctly. For information on Siebel EAI, see Overview: Siebel Enterprise Application Integration.
- If you have used Siebel Enterprise Integration Manager to set up batch processing jobs, then verify Siebel Enterprise Integration Manager is configured correctly. For information on Siebel Enterprise Integration Manager, see Siebel Enterprise Integration Manager Administration Guide.
- If you customized the style sheet or Web template files in the previous release, then reimplement those customizations in the new release as desired.
Perform System Tests
- 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
|