Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.4 HotFix 3
  • All Products

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

Configuration Guide

Configuration Guide

Back Next

Specify the Highest Reserved Key

Specify the Highest Reserved Key

The highest reserved key is the highest source system key. To ensure that the keys that the
MDM Hub
 generates does not conflict with the source system keys, reserve the highest source system key. When you preserve the source system keys, you can specify the highest source system key to use for the records.
To insert a gap between the source keys and the keys that the
MDM Hub
 generates, specify the number by which the key value must increase after the first load.
Set the highest reserved key value to the upper boundary of the source system keys. To allow a margin, set the number slightly higher by adding a buffer to the expected range of source system keys.
The load operation can add a record to the base object that does not contain the source system key. If the base object record does not contain the source system key, the
MDM Hub
 assigns a key that is higher than the highest reserved key value.
If you specify the highest reserved key, the
MDM Hub
 processes the ROWID_OBJECT value for the records that it loads in to the base object in the following way:
  1. During the initial data load, the
    MDM Hub
     takes the value in the PKEY_SOURCE_OBJECT column of the staging table. The MDM Hub inserts the value into the ROWID_OBJECT column of the base object instead of generating internal keys.
  2. After the initial data load, the
    MDM Hub
     resets the starting position of the key to the value of the highest reserved key that is incremented by 1.
  3. The
    MDM Hub
     uses the highest reserved key value for subsequent loads from the staging table. The
    MDM Hub
     uses the key that it generates for loads from other staging tables. The key that the
    MDM Hub
     generates is in continuation with the highest reserved key value.
You can preserve the source system keys for one staging table associated with a base object even if the keys are from the same source system. Set the reserved key range at the initial load.
0 COMMENTS
We’d like to hear from you!