|
Upgrade Guide > How to Perform a Siebel Database Upgrade >
Process of Upgrading a Siebel Production Test Environment
Upgrades: All Siebel upgrades. Environments: Production test environment only. Does not apply to production environment. This process is part of a road map. See Road Map for Performing a Siebel Database Upgrade. This topic lists the steps required to upgrade to a production test environment to the current release. Print this topic and use it as a checklist for doing the upgrade. The topic is divided into sections, each containing a list of numbered steps. Complete each section in the order shown. 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 on Oracle's 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.
- 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 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 manually enter the customizations in the upgraded environment. 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.
Upgrade the RDBMS
- 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.
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 Server and the Siebel Gateway Name Server.
- Verify that there are no open database connections.
- 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.
- Execute runstats on the Siebel Database. This will improve upgrade performance.
Pre-Upgrade Tasks for Oracle
- 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 MS SQL Server
- Perform the tasks in Preparing an MS SQL Server Database for a Siebel Upgrade.
- Run MS SQL Server statistics. This will improve upgrade performance.
Pre-Upgrade Tasks for Application Data
- Perform the tasks in Technical Note 521 on Oracle's Siebel SupportWeb. Table 16 shows the applicability of the tasks in the Technical Note.
Table 16. Tasks in Technical Note 521
|
|
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 the Technical Notes and Alerts on Oracle's Siebel SupportWeb shown in Table 17.
Table 17. Technical Notes and Alerts
|
|
Technical Note 481 |
Development only |
- Perform the tasks in Preparing Siebel Application Data for Upgrade.
Prepare the Siebel Database for Upgrade
- Refer to Technical Note 586 on Oracle's Siebel SupportWeb for instructions on how to set up the Siebel Database and Siebel Servers in the production test environment.
- Copy upgrade files to the environment:
- Moving the Siebel Repository Files.
- Custom SRF file.
- Reports files.
- Copying UI Files to a New Siebel Environment.
- If you revise repository objects or schema definitions, regenerate the schema.ddl and custrep.dat files. See Regenerating the Siebel Repository Definition Files.
- Verify the production test database is either a copy of the current production database or has the same topology and amount of data.
This is important for effective upgrade tuning before performing the production upgrade.
- Back up the production test environment database. (If you backed up the database as part of an RDBMS upgrade, ignore this step.)
To do upgrade tuning, you will restore this database and perform test-upgrades on it.
- (Optional) Changing the Siebel Database Server Configuration Utilities Language.
- Verify that you have defined ODBCs for connecting to the development environment database and the production test environment database. See Verifying the Oracle Database ODBC Definition for a Siebel Upgrade.
- Run the Database Server Configuration Utilities:
- (Optional) Identifying and Dropping Obsolete Indexes for a Siebel Upgrade.
Upgrade Siebel Database Schema (upgrep)
- Run the Database Server Configuration Utilities:
- Review the following topic and perform the procedure if applicable: Identifying and Dropping Obsolete Indexes for a Siebel Upgrade.
- Edit generated SQL files as required by Siebel Technical Notes, Alerts, Release Notes or other publications. For a complete list, see the Installation and Upgrade Portal page on Oracle's Siebel SupportWeb.
- Resume the upgrade: Starting the Siebel Upgrade Wizard.
- 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.
- If errors occurred because you entered incorrect information in the Database Server Configuration Utilities, see Regenerating SQL Files for a Siebel Upgrade.
- Rerun the Database Server Configuration Utilities.
- 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.
- Back up the upgraded database.
Upgrade Custom Database Schema (upgphys)
- Run the Database Server Configuration Utilities:
- 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 Database Server Configuration Utilities.
- Manually Archiving Siebel Upgrade Log Files.
- Installing New Siebel License Keys During an Upgrade.
- Back up the upgraded 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.
- Upgrading to Siebel RC2 or AES Encryption.
- Generate a Siebel Remote database template file. See Siebel Remote and Replication Manager Administration Guide.
- (Oracle database 9i and later). Set Optimizer Mode to CBO.
- Run database statistics.
NOTE: The upgrade is complete. The remaining sections deal with configuration and validation tasks.
Postupgrade Tasks for Applications Configuration
- 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 eBusiness Application Integration Volume I.
- 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.
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
|
