1. Database Upgrade Guide
  2. Migrating Household Relationships to the Party Model

Migrating Household Relationships to the Party Model

To check household data integrity and support migration of household data to the Party model, you must run the household verification script (HH_MIG_populate.sql).

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 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 and generates a report based on an output file. Output is in the form of row IDs. The script verifies that every household associated with an entity includes a contact associated with that entity.

If there is no output, then this means data integrity is good, and no action is required. If you receive output, then you must examine the relationship between contacts and households.

To run the household verification script

  1. Run one of the following household verification scripts as required:

    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 is the tableowner

    • Password is the tableowner password

    • ODBCDataSource is the data source of the database

    • OutputFileLocation is the location of the output file:

      • Windows: SIEBEL_ROOT\log\HH_Mig_populate.txt

      • UNIX:$SIEBEL_ROOT/log/HH_Mig_populate.txt

    • LogFileLocation is the location of the log file:

      • Windows: SIEBEL_ROOT\log\HH_Mig_populate.log

      • UNIX: $SIEBEL_ROOT/log/HH_Mig_populate.log

    • ScriptLocation is the 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\DB2\HH_Mig_populate.sql /v y

  2. If you receive output, then review the temporary table and check 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.