Bookshelf Home | Contents | Index | Search | PDF

Upgrade Guide for Microsoft Windows > 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 table TEMP_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 at the DOS command prompt:

  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 y

  where:

  Tableowner = Tableowner

  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)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)

  Example:

  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 y

  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.

  Output is in the form of row IDs.

  • If there is no output, no action is required. Data integrity is verified between Release 6.x and 7.x.
  • If you do receive an output, this means that no contact is associated with the household for a particular entity. This can occur in the following scenarios:
    • Contact is correct and household is incorrect.
    • Contact is incorrect and household is correct.
    • Contact is incorrect and household is incorrect.

      At least one contact associated with an entity must also be associated with the household for that entity.

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.

Review the following tables:

• S_CONDITION
• S_PROD_BNFT

To prevent loss of data, perform the following procedure before you upgrade to Release 7.x.

To prepare S_CONDITION and S_PROD_BNFT for upgrade

1. Review records in S_CONDITION for records that contain more than 200 characters.
2. For records which contain more than 200 characters, edit the records so that their row length is less than 200.
3. Repeat this procedure for S_PROD_BNFT.

Bookshelf Home | Contents | Index | Search | PDF