Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Customer 360
  3. Before You Install
  4. Installing MDM - Customer 360
  5. After You Install
  6. Business Processes for Customer Management
  7. Customizing Customer 360
  8. Upgrading Customer 360
  9. Troubleshooting

Step 3. Update Foreign Keys and Recalculate Best Version of Truth

Step 3. Update Foreign Keys and Recalculate Best Version of Truth

After you apply the
update_foreign_keys.change.xml
change list, update the foreign keys and recalculate the best version of truth for the records. After you recalculate the best version of truth, verify whether the best version of truth is successfully calculated for all the records.
  1. Open a command prompt, and go to the following directory:
    <MDM installation directory>/app/tcr/datamodelmigration/bin
  2. To update the foreign keys, run the following command:
    • On Windows.
      migrate_to_party_model.bat update_foreign_keys
    • On UNIX.
      migrate_to_party_model.sh update_foreign_keys
  3. To recalculate the best version of truth for the records, run the following command:
    • On Windows.
      migrate_to_party_model.bat update_BVT
    • On UNIX.
      migrate_to_party_model.sh update_BVT
  4. To verify whether the best version of truth is calculated for all the records, perform the following steps:
    1. Run the following command:
      • On Windows.
        migrate_to_party_model.bat verify_data_update
      • On UNIX.
        migrate_to_party_model.sh verify_data_update
    2. Open the following log file:
      <MDM installation directory>/app/tcr/datamodelmigration/log/verify_data_update.log
      The log file displays the number of records that failed the best version of truth calculation for each base object. The value 0 indicates that the best version of truth is calculated for all the records.
      The following sample log entry indicates that the best version of truth is calculated for all the records in the C_BO_PRTY_RLE_STCK_EXCH table:
      0 rows affected TABLE_NAME,COUNT(1) C_BO_PRTY_RLE_STCK_EXCH,0
  5. To delete the configuration details that are irrelevant to the data model based on the Party table, run the following command:
    • On Windows.
      migrate_to_party_model.bat delete_configuration
    • On UNIX.
      migrate_to_party_model.sh delete_configuration

0 COMMENTS

We’d like to hear from you!