Siebel IRM on the IBM DB2 for z/OS RDBMS: List of jobs to run a Siebel Production Upgrade
Last updated on NOVEMBER 16, 2015
Applies to:Siebel CRM - Version 15.0 [IP2015] and later
Information in this document applies to any platform.
The present document is applicable only to Incremental Repository Merge (IRM) executions for Siebel CRM implementations on the IBM Db2 for z/OS RDBMS.
If you have completed a production test upgrade and have tuned the SQL and JCL upgrade files on the z/OS host, you can use these files to perform the target database upgrade in the production environment. On this article we lists the jobs that will need to be run in order to migrate a copy of your Siebel schema for which the JCL / SQL was already generated. First some background, though:
With this Siebel upgrade type, the concept of target and staging Siebel schema is introduced.
Target: Is the actual Siebel schema we are planning to migrate to the new Siebel CRM release, this can be for the Siebel CRM development, test, UAT or production environment.
Staging: This is a copy of the target Siebel schema we are planning to migrate. In order to create this copy as part of the Siebel upgrade process, the Siebel schema definition is read from the Siebel Repository available from the target environment, in this sense it's important that prior starting the Siebel Upgrade process both logical and physical schema on target are in sync (e.g. ddlsync was executed and its changes were applied on the old Siebel CRM release);
The Siebel upgrade on the IBM DB2 for z/OS RDBMS is designed in a way to minimize the impact on the target Siebel schema. For this to happen, the staging schema is used to generate all JCL and SQL.
This list of jobs will then be modified to be eventually executed on target. Based on this list of modified jobs, our Siebel CRM customers implementing on the IBM DB2 for z/OS RDBMS can then plan to migrate the target schema as well as copies of the same environments.
A good example is for the Siebel CRM production environment upgrade where it's good practice to run, in preparation to the actual production roll out, mock upgrades (test production upgrades) of copies of the Siebel production schema. Once this production test environment upgrade was completed successfully and we are happy with the results, the same JCL/ SQL used to migrate this environment can be re- used to migrate copies of the same environment (and, eventually, the actual Siebel production database, when we are ready for it).
This process is documented on the Siebel Bookshelf under:
Siebel Database Upgrade Guide for DB2 for z/OS > How to Perform a Siebel Database Upgrade > Process of Upgrading a Siebel Production Environment
"Upgrade the Siebel Database Schema (upgrep + upgphys)" section.
Use the My Oracle Support Community, Siebel Installation and Upgrade (MOSC) for questions and answers on the Siebel Upgrade process:
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