Bookshelf Home | Contents | Index | PDF |
Siebel Database Upgrade Guide > Preparing Siebel Application Data for Upgrade > Preparing Siebel Customized Seed Data for UpgradeUpgrades from: All Supported Siebel releases. Environments: Development, production test, 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:
Before starting the upgrade, evaluate whether you need to 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. The ROW_ID value for 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 field stores the date when the record was last updated. If you modify a seed data record, 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, the ROW_ID 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 seed data records as follows:
For 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. To discard seed data modifications
Related Topics |
Siebel Database Upgrade Guide | Copyright © 2008, Oracle. All rights reserved. | |