Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Recalculate Base Object Jobs

Recalculate Base Object Jobs

Recalculates the best version of the truth for all base objects if you do not use the ROWID_OBJECT_TABLE parameter to identify base objects to recalculate.
Run the Recalculate Base Object job after you change trust settings or validation settings. The MDM Hub does not recalculate the best version of the truth after you change the trust setting or validation setting even if it synchronizes metadata. If you do not recalculate the best version of the truth after you change the trust settings or validation settings, the best version of the truth might be outdated.
You can run the Recalculate Base Object job with or without the ROWID_OBJECT_TABLE parameter. If you run the job with the ROWID_OBJECT_TABLE parameter, the MDM Hub recalculates the best version of the truth for all base objects identified by the ROWID_OBJECT column in the table/inline view. Brackets are required around inline view. If you run the job without the ROWID_OBJECT_TABLE parameter, the MDM Hub recalculates the best version of the truth for all records in the base object. The MDM Hub recalculates the records in batch sizes of MATCH_BATCH_SIZE or a quarter of the number of the records in the table, whichever is less.

0 COMMENTS

We’d like to hear from you!