Last updated on JULY 28, 2017
Applies to:Siebel System Software - Version 8.0 SIA  and later
Siebel CRM - Version 8.0 SIA  and later
Information in this document applies to any platform.
This document gathers some of the common questions and 'stumble blocks' for the Siebel upgrade process.
When do we speak of Siebel upgrade?
You execute a Siebel upgrade process when you migrate your Siebel CRM application from one major Siebel CRM release to another, such as, for instance:
From Siebel SIA version 7.8.2 to version 8.1.1.x
From Siebel SIA version 8.0 to version 8.1.1.x
You also execute a Siebel upgrade process when you migrate your Siebel SEA (horizontal release) application/ schema to SIA (industry application), such as in the following examples:
From Siebel SEA version 7.8.2 (or 8.0) to Siebel SIA version 8.1.1.x
From Siebel SEA version 8.1.1.x to Siebel SIA version 8.1.1.x
The most common Siebel upgrade paths are discussed on the following advisor:
Upgrade Advisor: Siebel from Earlier Releases to 8.1.1.x or 8.2.2.x: <Document 259.1>
Visit the My Oracle Support Community, Siebel Installation and Upgrade for common questions, around the Siebel upgrade process topics and exchange with the Siebel community along with the Global Customer Support engineers.
On the other hand, if your Siebel CRM application is already at SIA 8.1.1.x level (where 'x' is between 0 and 14, such as, Siebel SIA version 126.96.36.199), in order to migrate to the latest Siebel Innovation Pack (currently IP2015 or Siebel CRM version 15.0), you must execute the new Incremental Repository Merge (IRM) process.
This is discussed on the IP2015 Siebel Database Upgrade Guide at: Performing the Siebel Incremental Repository Merge
Visit the My Oracle Support Community, Siebel IRM for common questions, around the Siebel IRM process topics and exchange with the Siebel community along with the Global Customer Support engineers.
A translated version of this document is available as 'Important information for a successful Siebel version 8.x upgrade for Japanese customers', Doc ID 1502300.1.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms