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: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Server Caching and MDM Hub Console Locks

Server Caching and MDM Hub Console Locks

When no locks are in effect in the
Hub Console
, the
Hub Server
caches metadata and other configuration settings for performance reasons. When a
Hub Console
user acquires a write lock or exclusive lock, caching is disabled, the cache is emptied, and
Informatica MDM Hub
retrieves this information from the database instead. When all locks are released, caching is enabled again.
When more than one
Hub Console
uses the same
Operational Reference Store
, a write lock on a
Hub Server
does not disable caching on the other Hub Servers.

0 COMMENTS

We’d like to hear from you!