|Bookshelf Home | Contents | Index | PDF|
To upgrade your Siebel database from one release of Siebel Business Applications to another, you must follow the general taskflow outlined in this chapter. This taskflow is, however, general and does not include certain key specifics. For specific tasks associated with each task area, see the chapters and specific topics cross-referenced throughout this chapter.
The examples in this chapter refer to a Development environment. If you have a Development environment, you must upgrade it first, before upgrading other environments. This merges your customizations with the new release. A merged repository file and database schema file are created and become inputs to the production test environment upgrade and production upgrade.
Figure 1 shows a simplified task flow which highlights the general task flow of upgrading your Development Environment. Each chapter in this book which contains tasks related to your upgrade (as opposed to conceptual information) will contain this graphic, as well with the area of interest highlighted to illustrate where you are in the upgrade process.
When upgrading the infrastructure, first consult OracleMetalink 3 for any Bulletins or Alerts which might be applicable to your installation scenario. Additionally, upgrade all Siebel Server software and other server related software, as well as any third party infrastructure software, and your RDBMS.
Alerts point out key product behavior and important change requests and are often of a time-critical nature. An alert typically includes a description or symptoms of an issue and a recommended action, such as a workaround or application of a maintenance release or fix pack.
For information on Best Practices, see Upgrade Planning Best Practices. For information on specific tasks, see Process of Upgrading a Siebel Development Environment.
Chapters that include information on Phase 2 include Basic Database Preparations for a Siebel Upgrade. Use this chapter for information on preparing your database for your Siebel Upgrade.
Pre-upgrade tasks include verifying Siebel database connectivity, making sure there are no pending workflows, preparing Siebel tables and objects, performing database preparation, including stopping Siebel Servers, and making sure the Siebel Gateway Name Server remains up and running.
In this phase you will back up your development database, install the new version of Siebel Tools, rename your existing Siebel Repository, and run the Database Configuration Wizard and the Upgrade Wizard.
The Database Configuration Wizard collects information about the upgrade process you want to perform, stores all collected data in a master upgrade file. The SQL generator creates SQL files from these data.
For more information on upgrading the database schema, see Upgrade Siebel Database Schema (upgrep). This topic is part of the process topic, Process of Upgrading a Siebel Development Environment, which walks you though the Upgrade process in greater detail.
You prepare for and perform the Repository merge in Siebel Tools. Repository tables store the definitions of the objects used to build your Siebel Application, along with schema definitions. The repository merge process preserves prior customizations by comparing Prior Customer Repository (the repository from your previous release), the New Siebel Repository (the unaltered repository from the current Siebel release), Prior Siebel Repository (unaltered Siebel repository from the previous release) and merges the content into a fourth repository called the New Customer Repository.
For information on all tasks leading up to and including the Repository merge, see Performing the Siebel Repository Merge.
Following a successful Repository merge, you run the postmerge utilities to make revisions to objects in the New Customer Repository. The utilities are useful for identifying problems with previous UI customizations. For more information on the Postmerge Utilities, see Running the Siebel Postmerge Utilities.
Additionally, you will review the Siebel user interface to make sure no postmerge issue have arisen. Also, you will review objects that were deleted from the Siebel Repository, review objects made obsolete by the new release, and so on. For more information, see Reviewing the Siebel User Interface and Siebel Postmerge Development Tasks.
At this stage of the upgrade process, you reapply previous schema customizations and perform other verification and validation efforts on your database environment. For more information, see Postupgrade Tasks for the Siebel Database and File System.
Additionally, you will install new license keys for your Siebel Business applications, activate and deploy workflows, and other tasks related to getting your Siebel Business Applications up and running. For more information, see Postupgrade Tasks for Siebel Applications.
For information on the repository definition files, see Regenerating the Siebel Repository Definition Files.
|Siebel Database Upgrade Guide||Copyright © 2008, Oracle. All rights reserved.|