Minimizing Downtime During Production Upgrade
(Doc ID 478308.1)
Last updated on JULY 27, 2023
Applies to:
Siebel System Software Upgrade - Version 7.8 [19021] to 16.0 [IP2016] [Release V7 to V16]Siebel CRM - Version 7.8 [19021] to 16.0 [IP2016] [Release V7 to V16]
Information in this document applies to any platform.
Area(s):Upgrade
Release(s):V7 (Enterprise), V7 (Professional), V7 (MidMarket), V8 (Enterprise), V8 (Professional)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V8 (Enterprise)
Keywords:Upgrade, Minimize, Downtime, best practices, schema, read only, environment
This document was previously published as Siebel Technical Note 616.
Purpose
This Technical Note is based on Upgrades to Siebel 7.8 however is compatible with Upgrades to other Siebel 7.x versions, Siebel 8.0, Siebel 8.1, Siebel 8.2 and IPx.
Since the allowable downtime window, hardware resources, and deployment size varies significantly from one customer to another, there is no unique best practice process that can be prescribed for all customers. However, a few base line processes that are mostly applicable for all upgrades will be described here independent of these factors. Certain changes to the best practices described here may be needed to meet specific requirements.
The appropriate documentation in Siebel Bookshelf and on My Oracle Support should still be referred to for detailed instructions on transitioning from the production test environment to production, and on installation and configuration of the Siebel Enterprise, Siebel Tools client, and supported 3rd party applications.
The following table shows the key attributes of three best practices described here:
|
Best Practice
|
Database Upgrade
|
Enterprise Upgrade
|
3rd Party Applications
|
Additional Hardware
|
Service Offering
|
|
1. High Availability Upgrade Service
|
Minimal downtime with Expert Service offering
|
Minimal Downtime with Binary Co-existence
|
Re-install
|
Yes (Duplicate Production DB Server)
|
Yes
|
|
2. Read-only access for users
|
Read-Only access for users
|
Minimal Downtime with Binary Co-existence
|
Re-install
|
Yes
(Test Production DB Server)
|
No
|
|
3. Baseline Process
|
System outage for users
|
Minimal Downtime with Binary Co-existence
|
Re-install
|
No
|
No
|
Scope
This document is informational and intended for any user.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| Best Practice 1: High Availability Upgrade Service |
| Best Practice 2: Read-Only Access for Users |
| Best Practice 3: Baseline Process |
| References |