Bookshelf Home | Contents | Index | PDF |
Siebel Database Upgrade Guide > Application Planning for a Siebel Upgrade > Upgrade Planning for Migrating Siebel Address Data
NOTE: This topic does not apply to Siebel Business Applications (HOR) that you are upgrading to a later release of Siebel Business Applications (HOR). Siebel 7.7 (and Siebel 7.5 SIA) changed the way address information is stored. You must perform several tasks to ensure address migration is handled correctly. Previous ReleasesIn previous releases, address data was stored as follows:
Siebel 7.7In Siebel 7.7, the relationship between person and address and between account and address is M:M. Address information is stored in S_ADDR_PER. The relationship between addresses and contacts and between addresses and organization is stored in S_CON_ADDR. The upgrade process revises storage of address data as follows:
How Address Data Is PreservedBecause PER_ID is no longer part of the user key for S_ADDR_PER, the ADDR_NAME must be unique for all records. It is possible that records within or across S_ADDR_ORG and S_ADDR_PER could have the same ADDR_NAME. If this occurs, the ADDR_NAME for one of the records is preserved, and the upgrade process appends the ROW_ID to ADDR_NAME for the others. This prevents records from being deleted and preserves all records from both tables. How to Manage Address MigrationYou must perform the following tasks to migrate address data:
To manage address migration, follow the steps in Process of Upgrading a Siebel Production Test Environment. Each of the address migration tasks is included as a step in this process. Each step refers you to a procedure for performing the task. |
Siebel Database Upgrade Guide | Copyright © 2008, Oracle. All rights reserved. | |