Overview of Siebel Database Environments

This chapter provides an overview of the upgrade process of the three Siebel database environments (development, test, and production). It includes the following topics:

Note: For a detailed overview of the upgrade process and related tasks, see Overview of Performing a Siebel Database Upgrade

Supported Upgrade Paths for Siebel 2018

The following table lists supported upgrade paths. The current release for this guide is Siebel 2018 (Siebel CRM update 18.12). The repository for the current release is SIA in all cases. For more information on terminology, see Terms Used in This Guide.

Siebel Repository consists of a Runtime Repository. This repository contains the compiled repository definition. This Runtime Repository is available for all of the supported Siebel languages. Siebel clients and servers now read the compiled definition from the runtime repository stored in the database. The Runtime Repository is required for either of the following upgrade tasks summarized in this topic.

If you run incremental repository merge for an existing Siebel database.
If you perform a full database upgrade for an existing Siebel database.

You also require the Siebel Runtime Repository to run Siebel Business Applications after you install a new Siebel database for Siebel CRM update 18.12. For more information, see theSiebel Installation Guide.

Note: After installing the Siebel CRM software for the current release, you must reset any passwords stored in the Siebel Gateway that were previously encrypted using RC4 encryption. In the current release, such passwords are encrypted using Advanced Encryption Standard (AES) instead of RC4. You must perform this task for any type of upgrade from versions prior to Siebel Innovation Pack 2014. For more information about reencrypting passwords, see Siebel Security Guide.

The following table lists the supported upgrade paths for Siebel CRM update 18.12.

Table Supported Upgrade Paths for Siebel CRM Update 18.12

Current Version	Target Upgrade Update	Upgrade Approach	Upgrade Tasks
Siebel CRM version 7.5.3 through Siebel CRM version 7.7.2 (SEA or SIA repository)	Siebel CRM update 18.12	New installation of Siebel 2018 (update 18.12) for upgrade. Full database upgrade. Two-step repository upgrade.	You must perform a two-step repository upgrade: Upgrade Siebel CRM version 7.5.3 through Siebel CRM version 7.7.2 (SEA or SIA repository) to Siebel CRM version 8.1.1 (SEA or SIA repository). Upgrade Siebel CRM version 8.1.1 (SEA or SIA repository) to Siebel CRM update 18.x or later. Note: Use incremental repository merge for upgrades from Siebel CRM version 8.1.1 (SIA repository).
Siebel CRM version 7.8.2 (SEA or SIA repository)	Siebel CRM update 18.12	New installation of Siebel 2018 (update 18.12) for upgrade. Full database upgrade. Single-step repository upgrade.	Perform a full database upgrade. A Development environment upgrade and a Production environment upgrade are required. Upgrade directly to Siebel CRM update 18.12. It is a single-step repository upgrade and post-upgrade process. The New Customer Repository, generated through a three-way repository merge, contains all of the update content from Siebel CRM update 18.12. For more information about repository merge, see Performing the Siebel Repository Merge.
Siebel CRM version 8.0 (SEA or SIA repository)	Siebel CRM update 18.12
Siebel CRM version 8.1.1.0 through 8.1.1.7 (SEA repository)	Siebel CRM update 18.12
Siebel CRM version 8.1.1.0 through version 8.1.1.14 (SIA repository)	Siebel CRM update 18.12	Migration installation of Siebel CRM version 17.0. Migration installation of Siebel 2018 (update 18.12). Incremental repository merge.	Run the Siebel 2018 (update 18.12) installer to install Siebel 2018 (update 18.12) binaries. Use incremental repository merge to bring the repository to update 18.12. Note: This step is mandatory to be able to run Siebel Business Applications in the current release. For more information, see Performing the Siebel Incremental Repository Merge.
Siebel CRM version 8.2 (SIA repository)	Siebel CRM update 18.12	New installation of Siebel 2018 (update 18.12) for upgrade. Full database upgrade. Single-step repository upgrade.	Install the Siebel 2018 (update 18.12) binary files. Perform a full database upgrade. A Development environment upgrade and a Production environment upgrade are required. Upgrade directly to Siebel CRM update 18.12. It is a single-step repository upgrade and post-upgrade process. The New Customer Repository generated through a three-way repository merge contains all of the update content of Siebel CRM update 18.12. For more information about repository merge, see Performing the Siebel Repository Merge.
Siebel CRM version 8.2.1 (SIA repository)	Siebel CRM update 18.12
Siebel CRM version 8.2.2.0 through version 8.2.2.14 (SIA repository)	Siebel CRM update 18.12	Migration installation of Siebel CRM version 17.0. Migration installation of Siebel 2018 (update 18.12). Incremental repository merge.	Run the Siebel 2018 (update 18.12) installer to install Siebel 2018 (update 18.12) binaries. Use incremental repository merge to bring the repository to update 18.12. Note: This step is mandatory to be able to run Siebel Business Applications in the current release. For more information, see Performing the Siebel Incremental Repository Merge.
Siebel CRM version 15.0 through version 15.4	Siebel CRM update 18.12	Migration installation of Siebel CRM version 17.0. Migration installation of Siebel 2018 (update 18.12). Incremental repository merge.	Run the Siebel 2018 (update 18.12) installer to install Siebel 2018 (update 18.12) binaries. Use incremental repository merge to bring the repository to update 18.12. Note: This step is mandatory to be able to run Siebel Business Applications in the current release. For more information, see Performing the Siebel Incremental Repository Merge.
Siebel CRM version 15.5 and later	Siebel CRM update 18.12	Migration installation of Siebel CRM version 17.0. Migration installation of Siebel 2018 (update 18.12). Incremental repository merge.	Run the Siebel 2018 (update 18.12) installer to install Siebel 2018 (update 18.12) binaries. Use incremental repository merge to bring the repository to update 18.12. Note: This step is mandatory to be able to run Siebel Business Applications in the current release. For more information, see Performing the Siebel Incremental Repository Merge.
Siebel CRM version 16.0 and later	Siebel CRM update 18.12	Migration installation of Siebel CRM version 17.0. Migration installation of Siebel 2018 (update 18.12). Incremental repository merge.	Run the Siebel 2018 (update 18.12) installer to install Siebel 2018 (update 18.12) binaries. Use incremental repository merge to bring the repository to update 18.12. Note: This step is mandatory to be able to run Siebel Business Applications in the current release. For more information, see Performing the Siebel Incremental Repository Merge.
Siebel CRM version 17.0 and 18.x	Siebel CRM update 18.12	Single-step repository upgrade.	Install the Siebel 2018 (update 18.12) binary files. Upgrade directly to Siebel CRM update 18.12. It is a single-step repository upgrade and postupgrade process.

Terms Used in This Guide

This guide uses the following terms:

Database Upgrade. A set of standard procedures to migrate your custom repository and data schema from one release of Siebel CRM to a higher release level (that is, to a later release).
Siebel Innovation Pack and Siebel Patchset releases. Siebel Innovation Pack releases are installed either as new installations of Siebel CRM version 17.0 or as migrations from earlier releases of Siebel CRM version 8.1.1.x, version 8.2.2.x, version 15.x, or version 16.x. Siebel updates 17.x and 18.x are installed as patch installations into your Siebel Innovation Pack installation of 17.0. Starting with 18.x, Siebel updates might also have optional new feature content that includes optional repository changes. This guide is for upgrading to Siebel 17.x or 18.x from a previous Siebel installation prior to 17.0.
For more information about installing the current Siebel Innovation Pack release and about Siebel release types, see the Siebel Installation Guide. For more information about installing Siebel Patchset releases, including new features, see Siebel Patchset Installation Guide for Siebel CRM, 1614310.1 (Article ID) on My Oracle Support.
SEA and SIA. The Siebel Industry Applications (SIA) data model is physically a superset of the Siebel Enterprise Application (SEA) data model, which was formerly used. The SIA data model has more tables, more columns in the same tables, and more indexes than the SEA data model, but it does not exclude any tables, columns or indexes from the SEA version. Current versions of Siebel CRM now support only the SIA data model. Some upgrade paths might involve upgrading from an SEA data model to the SIA data model; additional steps apply.
Siebel Migration. Siebel Migration is a Web-based tool for end-to-end repository and data migration. Use Siebel Migration to migrate the repository, runtime repository, application workspace data, application data, application interface web artifacts and file system artifacts from a source environment to a target environment. Siebel Migration was previously known as the Repository Migration Utility (dev2prod).
The following topics deal with Siebel Migration:
Incremental Repository Merge. A mechanism which allows you to incrementally upgrade your custom repository data (including schema and seed data) from Siebel CRM version 8.1.1.x (SIA only), version 8.2.2.x, version 15.x, or version 17.x to Siebel CRM version 18.x. For more information about the incremental repository merge process, see Performing the Siebel Incremental Repository Merge.

Note: The Siebel CRM update 18.12 repository contains the cumulative repository, schema, and seed data for all new content (such as Release Features) developed up to Siebel CRM update 18.12.

Naming Conventions Used in This Guide

This guide follows several naming conventions:

All supported Siebel CRM releases refer to the upgrade path from which you might upgrade to a certain Siebel Business Applications release.
For more information about your upgrade applicability and for system requirements and supported platform certifications, see the Certifications tab on My Oracle Support.

Note: For Siebel CRM version 8.1.1.9 and later and version 8.2.2.2 and later, the system requirements and supported platform certifications are available from the Certifications tab on My Oracle Support. For more information, see article 1492194.1 (Article ID) on My Oracle Support. For earlier Siebel CRM versions, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.
Current release means the latest version of Siebel Business Applications.
The term Windows refers to all Microsoft Windows operating systems listed as supported for this release in the Certifications tab on My Oracle Support.
The term UNIX refers to all forms of the UNIX operating system listed as supported for this release in the Certifications tab on My Oracle Support.
The term IBM z/OS refers to the IBM mainframe operating systems that are collectively referred to as z/OS and listed as supported for this release in the Certifications tab on My Oracle Support.

About File Paths and Commands in Siebel Database Upgrade Topics

Environment variables and path placeholders for both Windows and UNIX paths are used throughout Siebel Database Upgrade Guide. Enter UNIX commands in a Korn shell. Enter Windows commands in a Windows Command Prompt window.

Windows Paths

The following path conventions specify file system locations in Siebel Database Upgrade Guide topics:

SIEBEL_ROOT is the absolute path of the Siebel Server installation directory. When you install a Siebel Server, the installation program queries for the path to the installation directory. The installation program then installs the Siebel Server in a subdirectory of this path called siebsrvr. For example, if you specified C:\sba81 as the installation directory for Siebel CRM 8.1, then SIEBEL_ROOT is C:\sba81\siebsrvr.
DBSRVR_ROOT is the absolute path to the Siebel Database Configuration Utilities on the Siebel Server. When you install the Siebel Database Server, the installation program queries for the path to the Siebel Server installation directory. The script then installs the Siebel Database Server files at the same level in a subdirectory called dbsrvr. For example, if SIEBEL_ROOT is C:\sba81\siebsrvr, then DBSRVR_ROOT is C:\sba81\dbsrvr. In this guide, many examples use the path C:\ and C:\sba81.
SIEBEL_TOOLS_ROOT is the directory in which Siebel Tools is installed, on a developer computer running Microsoft Windows.

UNIX Paths

The following environment variables and path conventions specify file system locations in Siebel Database Upgrade Guide topics:

SIEBEL_ROOT is the absolute path of the Siebel Server installation directory and also an environment variable that defines this path. When you install a Siebel Server, the installation script queries for the path to the installation directory. The script then installs the Siebel Server in a subdirectory of this path called siebsrvr. For example, if you specified /usr/siebel as the installation directory for Siebel CRM version 8.x, then $SIEBEL_ROOT is /usr/siebel/sba81/siebsrvr.
SIEBEL_ROOT and other environment variables required for doing an upgrade are located in siebsrvr/siebenv.sh andsiebsrvr/siebenv.csh. The Siebel Server installation script sets environment variable definitions in these shell scripts. Do not edit or delete these files.

Tip: Before performing command-line procedures in a shell window, you must source siebenv.csh for a C shell or source siebenv.sh for a Bourne shell. Doing this refreshes the environment variables required to run commands.
DBSRVR_ROOT is a path convention used in the Siebel Database Upgrade Guide. It is not an environment variable and is not defined in siebenv.csh or siebenv.sh.
DBSRVR_ROOT is the absolute path to the Siebel Database Server files on the Siebel Server. When you install the Siebel Database Server, the installation script queries for the Siebel Server installation directory. The script then installs the Siebel Database Server files at the same level in a subdirectory called dbsrvr. For example, if $SIEBEL_ROOT is /usr/siebel/sba8x/siebsrvr, then DBSRVR_ROOT is /usr/siebel/sba8x/dbsrvr. In this guide, many examples use the path /usr/siebel and /usr/siebel/sba8x.
Run UNIX scripts in a C or Korn shell. Do not run .ksh scripts in a Bourne shell.

Path Navigation

Procedural steps that ask you to navigate to a specified directory must be performed as follows:

Windows: Open a Command Prompt window and use the cd command to make the specified directory the current directory. Do not use the Windows File Explorer to navigate to the directory. For help with the cd command, enter the word help in the Command Prompt window and press Enter.
UNIX: In a shell window, make the specified directory the current directory.

Executing Commands

Procedural steps that ask you to execute a command must be performed as follows, unless specified otherwise:

Windows: In a Command Prompt window, verify the current directory is correct and enter the command. Do not run the command by entering it in the Run window in the Start Menu.
UNIX: In a shell window, verify the current directory is correct, source the siebenv script, then enter the command.

Because all versions of the UNIX operating system are case-sensitive, if you are running your Siebel Business Applications on UNIX, then treat all file names, directory names, path names, parameters, flags, and command-line commands as lowercase, unless you are instructed otherwise in the product.

If your deployment currently runs on Microsoft Windows, but you might switch to a UNIX environment or deploy UNIX servers in the future, then follow this same practice to avoid having to rename everything later.

About Supported Siebel Upgrade Paths

The supported upgrade paths for Siebel Business Applications are described in Supported Upgrade Paths for Siebel 2018 and in the Certifications tab on My Oracle Support.

Siebel Database Upgrade Guide does not cover the following specific upgrade paths or infrastructure changes. Contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle’s Application Expert Services.

Changing database platform type during an upgrade, for example changing from IBM DB2 to Oracle Database.
Changing operating system type during an upgrade, for example changing from Windows to UNIX.
Migrating to Unicode.
Migrating from Oracle’s Siebel Industry Solutions applications or Siebel Financial Services to Siebel Business Applications.
Upgrading from one base language to another. To achieve similar results, upgrade your existing base language and install the language pack for the desired language.

About Siebel Upgrade Environments

There are three Siebel database environments: Development, Production Test, and Production. If you have a development environment, then you must upgrade it first. When you upgrade your development environment your previous customizations are merged with the new release. The newly merged repository and schema definitions then become inputs to the production test environment upgrade and production upgrades which you will perform after completing the development environment upgrade.

If you do not have a development environment, or have not customized your repository, then no repository merge is required. You can use the repository and schema definition files included in the new release to upgrade your production test environment and production environment.

The production environment contains only the Runtime Repository and the required Design Time Repository. The production repository is extracted during the development upgrade.

Mapping Your Environments

You might have more or fewer environments than those described in About Siebel Upgrade Environments. The following table gives recommendations for mapping your environments to the ones used in Siebel Database Upgrade Guide.

Table Mapping Your Environments to Upgrade Processes

Environment Description	Recommended Upgrade
The environment has the following characteristics: It is used primarily for development with Siebel Tools. The Siebel database is a subset of your production database. The environment is not used for tech support or training. Developers are usually installed as Siebel Mobile Web Clients.	Development environment upgrade.
The environment has the following characteristics: It is intended for testing customizations before deploying them. It is where you tune your upgrade SQL files to minimize production upgrade time. There might be multiple upstream environments in addition to the production test environment. For example, these could include environments used by a product management group, Technical Support, and Quality Assurance.	Production test environment upgrade.
The environment is used for live business transactions by both local and remote users.	Production environment upgrade.

Environment Description

Recommended Upgrade

The environment has the following characteristics:

It is used primarily for development with Siebel Tools.
The Siebel database is a subset of your production database.
The environment is not used for tech support or training. Developers are usually installed as Siebel Mobile Web Clients.

Development environment upgrade.

The environment has the following characteristics:

It is intended for testing customizations before deploying them.
It is where you tune your upgrade SQL files to minimize production upgrade time.
There might be multiple upstream environments in addition to the production test environment. For example, these could include environments used by a product management group, Technical Support, and Quality Assurance.

Production test environment upgrade.

The environment is used for live business transactions by both local and remote users.

Production environment upgrade.

Siebel upgrade environments are described in detail in the following topics:

Development Environment

This environment is where developers use Siebel Tools to customize Siebel Business Applications, and where customizations are made to the Siebel Runtime Repository. When your Siebel Business Applications instance goes live in a production environment, the runtime repository is where all object definitions are retrieved, then displayed to users in your Siebel CRM user interface.

A development environment includes the following Siebel CRM modules:

Siebel Gateway
Siebel Server
Siebel Database Server files installed on a Siebel Server
RDBMS server and Siebel database
Siebel Application Interface
Siebel Tools installed on workstations running a supported Windows environment. This includes the local database running on developers’ Siebel Mobile Web Clients.
Siebel Business Applications and test data required to verify the basic function of Siebel Runtime Repository.

Upgrading the Development environment involves these tasks:

Prepare application data. These tasks prepare test data for migration.
Upgrade database (upgrep). You run the Database Configuration Wizard in upgrep mode. They perform a basic upgrade of the Siebel database schema and load repositories to prepare for the repository merge. Both upgrep and upgphys modes are run as a single step in the Database Configuration Utility.
Merge repository. You use Siebel Tools to merge your existing repository with the repository in the new release. Postmerge utilities upgrade form applets and verify that applets and views are configured correctly.
Run postmerge utilities. You use Siebel Tools to run a set of utilities that examine the merged repository. The utilities analyze your customizations and apply changes to them as needed to conform to the user interface in the new release.
Upgrade database (upgphys). You run the Database Configuration Utilities in upgphys mode. They further upgrade the Siebel database with changes resulting from the repository merge and complete the database upgrade.
The Database Configuration Utilities also generate the customer repository definition file and logical schema definition file that are used as input to the production test environment and production upgrades.

Note: During the synchronization process, custom columns in the Siebel schema that are not in the Siebel Repository are not deleted but custom indexes in the Siebel schema that are not in the Siebel Repository are deleted.

Production Test Environment

This environment is where an installed and fully upgraded development environment undergoes the quality assurance process. This part of your upgrade process allows you to tune upgrade performance in preparation for the transition to your live, production environment.

The production test environment includes the following Siebel CRM modules:

Siebel Gateway
Siebel Server
Siebel Database Server files installed on a Siebel Server
RDBMS server and Siebel database
Siebel Application Interface
All the Siebel Business Applications currently installed in your production environment
A copy of the Siebel database installed in your production environment

You perform the following processes in the production test environment:

Test the upgraded release to validate its function and performance before deploying it to users.
Tune the upgrade process to minimize the time required to perform your production upgrade.

Oracle provides an upgrade tuning application that analyzes how the upgrade scripts interacted with the production test environment database. The Upgrade Tuner enables you to tune how the scripts will execute against the Siebel database in your production environment. Tuning the scripts can significantly reduce the time required to complete the production upgrade. For this reason, the production test environment database must contain the same data volume and topography as your production database.

Upgrading the Production Test environment involves the following tasks:

Prepare application data. These tasks are about preparing application data for migration.
Upgrade database (upgrep). You run the Database Configuration Utilities in upgrep mode. They perform a basic upgrade of the Siebel database schema:
- You run the utility in Prepare for Production mode before running it in upgrep mode. The Prepare for Production mode reviews the upgraded development environment database schema and creates input files. The upgrep mode uses these files to make schema changes to the Siebel database.
- The upgrep mode imports the repository and schema definition files from the development environment upgrade. It uses these files to upgrade the Siebel database.
- The upgphys portion runs automatically. It makes several administrative changes to table data, including updating the schema version in S_APP_VER. It does not make schema changes.

Production Environment

The production environment is your live business environment, where your internal and external users interact with applications and generate actual business data. The production environment includes all your Siebel Enterprises worldwide.

The upgrade process assumes all production environment databases are completely separate from the development environment and production test environment databases.

Oracle provides these tools to help you transition from production test to production:

Siebel Application Deployment Manager (ADM). This module migrates administrative data such as lists of values (LOVs) from the production test environment to the production environment. For details, see Siebel Application Deployment Manager Guide.
Siebel Anywhere. This application builds distribution kits for remote users. For details, see Siebel Anywhere Administration Guide.

Upgrading the Production environment involves the following tasks:

Additive Schema Changes. This step is optional and is run in the production environment. You can run this mode of the Database Configuration Utilities without taking the database offline. This mode makes schema changes that do not affect the operation of the application. This reduces the amount of time the production database must be offline to perform the upgrade. Testing Additive Schema Changes is also included in the process checklist for tuning the upgrade. This allows you to verify Additive Schema Changes in the production test environment before running it in the production environment.
Prepare application data. These tasks are about preparing application data in the production database for migration.
Upgrade database (upgrep). In the production test environment, you start the Database Configuration Utilities in upgrep mode, and enter configuration information for the production environment. This includes an ODBC definition for connecting to the production Siebel database.
This step causes the wizard to use the SQL for upgrading the production test database to upgrade the production database.

The SQL generated for the production test database upgrade is preserved, and no new SQL is generated. This SQL has been tuned using the Upgrade Tuner and has been revised by the Prepare for Production mode. You do not have to repeat these two steps before upgrading the production database.

You do not have to run the Database Configuration Utilities in upgphys mode. The upgphys steps are included in the production environment upgrep.

Postupgrade Tasks

Following the upgrade you perform the following tasks:

Set up the environment. These tasks set up the postupgrade environment, which includes extracting the developers’ databases and running database statistics.
Application administration. These tasks set up the applications and include such tasks as setting up user access and visibility of views and screens.
Application configuration. These tasks prepare applications for testing, including data migration for specific applications.
Test the system. These tasks test the system. For development environment upgrades, you perform basic unit tests to verify the operation of the application. For production test environment upgrades, you perform a full suite of regression and stress tests to verify the system is ready for production.