1. Database Upgrade Guide
  2. Preparing Siebel Customized Seed Data for Upgrade

Preparing Siebel Customized Seed Data for Upgrade

Environments: Development, Test and Production.

Platforms: Windows, UNIX, IBM z/OS.

Modified seed data are not upgraded, even if the upgraded seed data are required for an application to run normally, with the following exceptions:

  • If you have modified seed data through the user interface or through Siebel Enterprise Integration Manager, then the repository merge preserves the modifications using the same logic as for other repository objects.

  • (Since Siebel CRM 8.0) Customizations to seeded workflows in the Prior Customer Repository are merged into workflows in the New Customer Repository by the repository merge process.

Before starting the upgrade, evaluate whether you must retain your seed data modifications. If practical, consider discarding the modifications. After the upgrade, you can reimplement those modifications that do not interfere with operation of applications.

Seed data are records provided in the Siebel database tables as part of a release. Seed data provides information needed to run a Siebel application. Examples of seed data are the values in a List of Values (LOV) definition, default mappings of views to responsibilities, and predefined queries.

Note: The paragraphs that follow provide a generalized description of how seed data for U.S. English (ENU) is imported during the upgrade process, including whether existing data is replaced. This description does not apply to all types of seed data, including seed data for non-ENU languages.

The ROW_ID value for ENU seed data records provided in a release begins with 0 (zero). In addition, these records have a default LAST_UPD value of 1980-01-01. The LAST_UPD column stores the date when the record was last updated.

If you modify an ENU seed data record, then the value of LAST_UPD is changed from 1980-01-01 to the date the modification was made. If you add a new seed data record, then the ROW_ID value does not begin with 0, and the LAST_UPD value is the record creation date.

When you perform the upgrep part of the upgrade, the dataimp utility upgrades ENU seed data records as follows:

  1. For records where the ROW_ID value begins with 0, it erases ENU seed data records where the value for LAST_UPD is 1980-01-01, unless prevented by scripting.

  2. Dataimp replaces these records with those contained in seed data files included in the release. In the new records, the value for LAST_UPD is 1980-01-01.

  3. Dataimp does not erase and replace seed data records where the value for LAST_UPD is later than 1980-01-01. Instead, for each of these records, dataimp writes an error to the log file. The error is benign and does not cause the upgrade to fail. Use these error entries to verify which seed data records were not changed.

For ENU seed data records you have modified, you can discard the modifications by changing the value of LAST_UPD to 1980-01-01. This causes dataimp to replace these records with those from the new release. For seed data records you have created, the upgrade process retains these records.