Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Considerations for Using Row-level Locking

Considerations for Using Row-level Locking

When using row-level locking in a
Informatica MDM Hub
implementation, consider the following issues:
  • A batch process can lock individual records for a significant period of time, which can interfere with
    access over the web.
  • There can be small windows of time during which
    requests will be locked out. However, these should be few and limited to less than ten minutes.
  • The
    Hub Store
    needs to be sufficiently sized to support the combined resource demand load of executing batch processes and
    requests concurrently.
Interoperabilty must be enabled if Batch jobs are being run together. If, you have multiple parents that attempt access to the same child (or parent) records when running different Batch jobs, one job will fail if it attempts to lock records being processed by the other batch and it holds them longer than the batch wait time. The maximum wait time is defined in C_REPOS_TABLE.


We’d like to hear from you!