Siebel Upgrade Clarification For Address Data Migration When Running Upgrep For Database Upgrade
(Doc ID 2590529.1)
Last updated on SEPTEMBER 24, 2019
Applies to:Siebel Sales - Version 22.214.171.124 SIA  and later
Information in this document applies to any platform.
Customer was preparing environment for upgrade and had a question. Customer had a question as below:
Do we need to perform the below two steps before Upgrep or after Upgrep and right before repository merge as mentioned in the Siebel Database Upgrade Guide?
• Before upgrading the database, you must run a script to identify records that have the same ROW_ID between S_ADDR_PER and S_ADDR_ORG. You must eliminate duplicate row IDs.
• You must evaluate whether to modify upgrade scripts to migrate address data in custom extension columns in S_ADDR_PER and S_ADDR_ORG. Review the new schema and determine whether your custom columns can be mapped to standard columns. If no matching standard columns exist, then create new columns on the target tables. During the database upgrep, you do this after running the Database Configuration Utilities but before running the Upgrade Wizard.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document