Upgrade Guide for DB2 UDB for z/OS > Preparing Application Data for Upgrade >

Verifying Household Data Integrity

Upgrades: Release 6.2.1 only.

Environments: Production test, production.

This topic is part of an upgrade process. See How to Perform the Upgrade.

If you choose to implement the new household design, you must run the household verification script (HH_MIG_populate.sql) before upgrading to Release 7.8.

If you choose not to upgrade to the new household design, do not run the script. Also, make sure that the temporary table TEMP_HH_OBJ_MIG does not exist in the database.

The household verification script verifies household data integrity. The script verifies that at least the same number of entities will belong to a household after the upgrade as belong to it before the upgrade. The script ensures that after the upgrade, you will see the same or more household data than before the upgrade.

The household verification script makes 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.

The script populates a temporary table with data, TEMP_HH_OBJ_MIG. The script generates a report based on an output file. Output is in the form of row IDs.

If there is no output, this means Siebel 6.2.1 data integrity is good, and no action is required. If you receive output, this means that no contact is associated with a household for a particular entity.

To run the household verification utility

1. Type the following command:
   • Windows:

     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

   • UNIX:

     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

     where:

     Tableowner = Tableowner

     Password = Tableowner password

     ODBCDataSource = Data source of the database

     OutputFileLocation = Location of the output file:

     • Windows: SIEBEL_ROOT\Log\HH_Mig_populate.txt
     • UNIX: $SIEBEL_ROOT/Log/HH_Mig_populate.txt

       LogFileLocation = Location of the log file :

     • Windows: SIEBEL_ROOT\log\HH_Mig_populate.log
     • UNIX: $SIEBEL_ROOT/log/HH_Mig_populate.log

       ScriptLocation = Location of the script:

     • Windows: DBSRVR_ROOT\database_platform\HH_Mig_populate.sql
     • UNIX: DBSRVR_ROOT/database_platform/HH_Mig_populate.sql

       Windows example:

       odbcsql /U Tableowner /P Password /S ODBCDataSource /a /c REM /separator / /O C:\sea7xx\siebsrvr\Log\HH_Mig_populate.txt /L C:\sea7xx\siebsrvr\Log\HH_Mig_populate.log C:\sea7xx\dbsrvr\DB2UDB\HH_Mig_populate.sql /v y

2. If you receive output, review the temporary table and verify the following for each contact. Make corrections as needed:
   • 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.