Bookshelf Home | Contents | Index | Search | PDF |
Upgrade Guide for UNIX > Preupgrade Tasks > Preparing Application Data for Upgrade >
Preparing Siebel Financial Services Data for Upgrade
NOTE: If you are upgrading from Release 7.x to Release 7.5, you do not need to perform this procedure.
This section provides additional preupgrade tasks for Siebel Financial Services customers upgrading from Release 6.x to Release 7.x of Siebel Financial Services. The tasks described in this section are unique to Siebel Financial Services and should be performed in addition to the preupgrade tasks for the development environment provided in the previous sections of this chapter.
Verifying Household Data Integrity
The household verification utility is unique to Siebel Financial Services. If you have chosen to implement the new household design, you must run this utility prior to the upgrade.
CAUTION: If you have elected not to upgrade to the new household design, do not run
HH_Mig_populate.sql
, and make sure that the temporary tableTEMP_HH_OBJ_MIG
does not exist in the database.When you migrate to the new household design, direct relationships between a household and its entities (Policy/Financial Accounts, Activities, Claims, Opportunities, Service Requests, and Companies) become obsolete. Therefore, you must run the household verification utility before the upgrade to verify data integrity. After the upgrade, you must be able to see greater than or equal to the amount of data that you had in Release 6.x.
The household verification script,
HH_Mig_populate.sql
, verifies that at least the same number of entities belong to a household after the upgrade as belonged to it in your previous release. This script is located in$SIEBEL_ROOT/dbsrvr/database_platform
directory.The household verification utility operates with the following assumptions:
- A household has at least one contact.
- The primary contact of a Policy/Financial Account is one of the contacts associated with this Policy/Financial Account.
- The primary contact of a Claim is one of the contacts associated with this Claim.
- The primary contact of an Opportunity is one of the contacts associated with this Opportunity.
- The primary contact of a Company is one of the contacts associated with this Company.
To run the household verification utility
- Type the following command:
odbcsql /U $Tableowner /P $Password /S $ODBCDataSource /a /c REM /separator / /O $OutputFileLocation/HH_Mig_populate.txt
/L $LogFileLocation/HH_Mig_populate.log $ScriptLocation/HH_Mig_populate.sql /v
Password
= Tableowner password
ODBCDataSource
= Data source of the database
OutputFileLocation =
Location and name of the output file (
$
SIEBEL_ROOT
/siebsrvr/Log/HH_Mig_populate.txt)
LogFileLocation =
Location and name of the log file($
SIEBEL_ROOT
/siebsrvr/Log/HH_Mig_populate.log)
ScriptLocation =
Location and name of the script($SIEBEL_ROOT/dbsrvr/database_platform/HH_Mig_populate.sql)
odbcsql /U $Tableowner /P $Password /S $ODBCDataSource /a /c REM /separator / /O /$SIEBEL_ROOT/siebsrvr/Log/HH_Mig_populate.txt /L /$SIEBEL_ROOT/siebsrvr/Log/HH_Mig_populate.log /$SIEBEL_ROOT/dbsrvr/database_platform/HH_Mig_populate.sql /v
The program populates a temporary table with data,
TEMP_HH_OBJ_MIG
. When the program has finished running, it generates a report based on your designated output file; for example,HH_Mig_populate.txt
.Preparing Application Tables for Upgrade
DESC_TEXT is a column that resides on two tables, S_CONDITION and S_PROD_BNFT. To broaden platform support, this column is reduced in length from 250 to 200 during the upgrade from Release 6.x to Release 7.x. Therefore, before you run the upgrade, examine these two tables for records that contain more than 200 characters. If you find oversized records, manually reduce the size of these records to 200 characters or less.
To prevent loss of data, perform the following procedure before you upgrade to Release 7.x.
Bookshelf Home | Contents | Index | Search | PDF |
Upgrade Guide for UNIX Published: 20 October 2003 |