Table 2. New Product Features in Siebel Database Upgrade Guide for DB2 for z/OS, Version 8.1
|
|
Migrating Siebel 6.2.1 Customizations |
Deleted this chapter because direct upgrades from Siebel CRM 6.2.1 to Siebel CRM 8.1 are not supported. |
About Terms Used in Siebel Database Upgrade Topics |
Modified topic. In this version of the guide, Release 7.x refers to all versions of Siebel CRM 7 from which you can upgrade directly to Siebel CRM 8.1; that is, versions 7.5.3, 7.7, or 7.8.2 only. |
About Supported Siebel Upgrade Paths |
Modified topic. Only upgrades from 7.5.3 and later to 8.1 are described in this version of the guide. |
About Siebel Additive Schema Upgrade Changes |
Modified topic. When an index is created during the additive schema upgrade process, and if the associated table contains data, the index must be defined with the DEFER YES parameter. This parameter ensures that the table is not locked while the index is being populated. |
About the Siebel Database Upgrade Process |
Modified topic. To upgrade to Siebel CRM version 8.1, you must run the Database Configuration Wizard in Prepare for Production Upgrade mode for upgrades from version 7.5.3 only. |
Roadmap for Upgrading from Siebel 6.x, 7.0.x, and 7.5.2 |
New topic describing how to upgrade to Siebel CRM version 8.1 from Siebel CRM releases earlier than 7.5.3. |
Upgrade Third-Party Software |
Modified topic. References to the Actuate Reports Server have been removed from this guide. Actuate products are not supported in the current release of Siebel Business Applications. |
Process of Upgrading a Siebel Development Environment |
Modified topic. Recommendations for when to run the RUNSTATS and the REORG utilities during the upgrade process have changed. |
Upgrade Custom Database Schema (upgphys) |
Modified topic. It is recommended that you issue an SQL DROP command to remove the Enterprise Integration Manager (EIM) tables from the database before synchronizing the Siebel logical and physical schemas. |
About Applying the DSNTIAUL Patch |
Modified topic. This topic now describes the DSNTIAUL patch, @@TIAUL USERMOD. |
Updating Group Names |
New topic. For development environment upgrades from Siebel CRM version 7.5.3, you must update table space group names before you prepare the storage control file used in the upgrade. |
Creating the Staging Database Schema DDL Files |
Modified topic. It is recommended that the DB2 subsystem name you specify for the staging or target database is the same as the ODBC Data Source Name (DSN) you specify for the database. |
Customizing the JCL UNIT Parameter Value |
New topic describing how to amend the UNIT=SYSDA parameter for the Job Control Language (JCL) generated for the Siebel CRM upgrade. |
Applying the Additive Changes in One Job |
Modified topic. To improve performance when additive changes are applied to the target database in one job, index creation jobs use the DEFINE YES, DEFER YES syntax. After applying the additive changes, you can rebuild the indexes. |
Renaming the Production Environment Repository |
Modified topic. To prevent a naming conflict, rename your existing production repository just before you take your production database offline to run the target database upgrade. |
Creating and Rebuilding Obsolete Indexes |
Modified topic. If you choose to rebuild obsolete indexes, it is recommended that you do so after you have completed the target database upgrade process. |
Deleting Redundant Upgrade Files |
Modified topic. This topic now includes information on how to delete stored procedures after the upgrade process is completed. |
Upgrade Files for Siebel Business Applications Version 8.1 |
Modified this chapter to reflect changes in the upgrade files that are generated for Siebel CRM 8.1. |
