Bookshelf Home | Contents | Index | PDF     

Upgrade Guide for DB2 UDB for z/OS > Postupgrade Tasks for Applications >

Reviewing Address Data After Upgrade

Upgrades:

  • From Release 6.2.1 of Siebel Financial Services applications to Release 7.8.x of Siebel Industry applications.
  • From Release 7.0.x of Siebel Financial Services applications to Release 7.8.x of Siebel Industry applications on all other platforms.
  • From Release 7.8.x of Siebel Business applications to Release 7.8.x of Siebel Industry applications on all other platforms.
  • This topic does not apply to Siebel Business applications (HOR) that you are upgrading to a later release of Siebel Business applications (HOR).

Environments: Production test, production.

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

The way address data is stored changed at Release 7.8. The upgrade migrated data from the table S_ADDR_ORG to S_ADDR_PER. The upgrade uses the following method for preserving address data:

  • If any records have the same value for ADDR_NAME within or across S_ADDR_ORG and S_ADDR_PER, the upgrade process preserves ADDR_NAME for one of the records and appends the ROW_ID to ADDR_NAME in the others.
  • If a record in S_ADDR_ORG has the same value for ADDR_NAME as a record in S_ADDR_PER, the upgrade process appends the ROW_ID to ADDR_NAME in one of the records.
  • The upgrade process truncates the value of ADDR_NAME to fit the size of the column.
  • The upgrade generates a report listing the records with duplicate ADDR_NAME within and across S_ADDR_ORG and S_ADDR_PER.

After the upgrade completes, review this report and edit or delete records from S_ADDR_PER as desired.

NOTE:  This report is also generated for 7.0.x Siebel Industry Solutions upgrades to 7.8 Siebel Industry applications. Ignore this report for these upgrades.

To review address records after upgrade

  1. Review the report generated by the upgrade:

    Windows: SIEBEL_ROOT\log\rpt_dup_addr_names.txt

    UNIX: $SIEBEL_ROOT/log/rpt_dup_addr_names.txt

  2. Use the report to identify records that are duplicates. For each set of duplicate records, the upgrade appended the ROW_ID to ADDR_NAME in one of the records.
  3. Use queries to edit records or delete duplicate and obsolete records.
    
Upgrade Guide for DB2 UDB for z/OS