1What’s New in This Release
What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.9 Update
The following information lists the changes in this revision of the documentation to support this release of the software.
Table What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.9 Update
Topic |
Description |
|---|---|
Modified topic. Updated the version numbers for supported upgrade paths. |
|
Modified topic. Describes how the orchestration.json file defines the migration process flow for migration resources. |
|
Modified topic. Describes how to execute a migration plan, including the following:
|
|
Using REST API with the Migration File Prepare and Deploy Service |
New topic. Describes the Migration File Prepare and Deploy Service. |
Modified topic. The username requirements for migration is that both source and target environments should have the same username and passsword. |
|
Example of a Siebel Development Environment Upgrade Flow (Steps That the upgphys Process Executes) |
Modified topic (Steps That the upgphys Process Executes). Clarified steps 8 and 9 as follows:
|
About Migrating with Siebel Migration z/OS About REST API Used for Migration Discovery and Execution Asynchronous Migration Using Siebel Migration Incremental Migration from a Development to a Production Environment Without Using Siebel Migration |
Modified topics. If your Runtime Repository Data Service or Incremental Runtime Repository Data Service migration plan does not include the non-mandatory Schema Service, then you must migrate any schema changes before executing the plan. |
New topic. As of Siebel CRM 8.1.x/8.2.x (including all Siebel Innovation Packs), the migration of user preferences is typically supported between releases. |
What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.7 Update
The following information lists the changes in this revision of the documentation to support this release of the software.
Table What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.7 Update
Topic |
Description |
|---|---|
Modified topic. Using the /z and /h parameters in the import command will reduce upgrade time and improve the overall repository import process performance. |
|
Modified topic. When validation completes, review the upgwiz.log and schema.log log files and correct any validation errors before running the validation process again. |
|
Modified topic. RepCrawler references the following files present in the
|
|
Modified topic. After execution of the Runtime Repository Data Service completes, you must do the following in the target environment: rename the Migrated Repository to Siebel Repository, restart Siebel Server, and activate workflow tasks. |
|
Modified topic. Migration logging has been enhanced to include logging for the following Siebel Migration resource operations:
|
What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.4 Update
The following information lists the changes in this revision of the documentation to support this release of the software.
Table What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.4 Update
Topic |
Description |
|---|---|
Modified topic. You are no longer prompted for schema username or password when creating (export/import only) migration plans for the following services
|
|
Modified topic. It’s no longer necessary to run the Schema Service along with the Runtime Repository Service, Application Workspace Data Service, or Incremental Runtime Repository Data Service. |
|
Modified topic. From 19.4 Update release onwards, the Schema Service is no longer automatically selected if any of the following services are selected when creating or editing a migration plan:
If you want to migrate schema using the UI, then you must select the Schema Service in the same migration plan or create a new plan.
Note: This condition does not apply when creating or editing a migration plan using REST. To run Application Workspace Data Service, Runtime Repository Data Service and Incremental Runtime Repository Data Service,
isSelected must be set to
True for the Schema Service as shown in the following example for Incremental Repository Data Service:
{
"name": "IRR",
"description": "IRR",
"source": "Source",
"target": "Target",
"resources": [
{
"name": "Incremental Runtime Repository Data Service",
"isSelected": "true"
},
{
"name": "Schema Service",
"isSelected": "true"
}
]
}
|
|
Modified topic. It is no longer necessary to do the following when performing a full Runtime Repository migration without using the Siebel Migration application:
|
What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.3 Update
The following information lists the changes in this revision of the documentation to support this release of the software.
Table What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.3 Update
Topic |
Description |
|---|---|
Modified topic. Siebel Migration does not support migration of repository or workspace data from non-development (RR) environments to other RR environments - migrating from Test to Production or UAT to Production is not permitted. Added tables listing the migration plan actions for the following migration services and the additional information that is required:
|
|
Modified topic. Added a table showing when the following migration scenarios are supported:
These migration scenarios are supported, using either the Siebel Migration application or REST API, in Siebel CRM 18.11 Update and later releases. |
|
|
Modified topic. Descriptions of the following migration services have been updated:
|
|
About Migrating with Siebel Migration z/OS |
Modified topics. From Siebel CRM 19.3 Update release onwards, the Siebel Migration application no longer supports the Design Repository Data Service. |
Using REST API with the Migration Design Repository Data Service |
Obsolete topic. The Siebel Migration application no longer supports the Design Repository Data Service. |
Modified topic. This topic lists some important issues to note when migrating configuration data and incremental changes. |
What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.1 Update
The following table lists the changes in this version of the documentation to support this release of the software.
Table What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 19.1 Update
Topic |
Description |
|---|---|
About the Siebel Database Configuration Utilities and Database Configuration Wizard |
Modified topic. As of Siebel Innovation Pack 2017, the Repository Migration Utility (dev2prod) is no longer supported. The Siebel Migration application is supported in Siebel Innovation Pack 2017 and later releases. |
New topic. Before upgrading to Siebel 17.x, Siebel 18.x or later, a number of parameters must be changed in the siebel.cfg file, otherwise the Siebel database upgrade will fail when upgrading in upgphys mode. |
|
Modified topics. During the Full Publish process, certain warning errors in the log file are acceptable and can be ignored. |
|
Incremental Migration from a Development to a Production Environment Without Using Siebel Migration |
New topic. Describes how to manually apply repository and schema changes to a target environment that is not in a Repository Upgraded state. |
New topic. Describes how to complete a synchronous full Runtime Repository (RR) migration without using the Siebel Migration application. |
|
New topic. Highlights some important information to consider when migrating configuration data and incremental changes. |
What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 18.12 Update
The following table lists the changes in this version of the documentation to support this release of the software.
Table What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 18.12 Update
Topic |
Description |
|---|---|
Modified topic. Development databases can use EBCDIC code pages. Databases with EBCDIC code pages support Merge and Full Publish functionality in a development environment upgrade. |
|
Modified topic. Migrating repository or data using Siebel Migration is not the same as performing a database upgrade where you migrate your custom repository and schema from one release of Siebel CRM to a higher release level. |
|
Modified topic. It is recommended that you back up your target database before starting to migrate repository or data using Siebel Migration. |
|
New topic. Describes how to use Siebel Migration to perform an asynchronous migration. |
|
Activating Workflows and Tasks in the Production Environment After Full Migration |
New topic. Workflows and tasks must be activated in the production (target RR) environment after a full migration. |
Modified topic. REST APIs can be used both before and after the repository upgrade is done. |
What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 18.11 Update
No new features have been added to this guide for this release. This guide has been updated to fix only bugs.
Table What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 18.11 Update
Topic |
Description |
|---|---|
New topic. Describes how to migrate a Siebel 18.8 Update or later release development environment to a target environment. |
What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 18.9 Update
The following table lists the changes in this version of the documentation to support this release of the software.
Table What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 18.9 Update
Topic |
Description |
|---|---|
|
New topic. Added information about using REST APIs with the Siebel Migration Application to do the following:
|
|
New topic. Added information about how to migrate a Siebel 18.8 Update or later development environment to a target environment. |
What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 18.8 Update
The following table lists the changes in this version of the documentation to support this release of the software.
Table What’s New in Siebel Database Upgrade Guide for DB2 for z/OS, Siebel CRM 18.8 Update
Topic |
Description |
|---|---|
New topic. Added a new topic that provides procedures for using Siebel Migration to generate a watermark. |
|
New topic. Added a new topic that describes the new orchestration.json file that defines the process flow for all the migration resources available in the Siebel Server. |
|
Modified topic. Added information about the Database Encoding parameter. |
|
Modified topic. Added information about viewing the package filename in the History tab. |
|
Modified topic. Added information about export and import asynchronous migration and information about the manifest file. Added information about configuring the Migration Package Location in the Siebel Management Console and added additional information about configuring the deployment package with Application Deployment Manager. |
|
Modified topic. Added information about how the File Prepare and Deploy Service reads the watermark file and what the service does with that data. |
Additional Changes
This guide has been has been updated to correct or remove obsolete product and component terms.