Table of Contents

Search

  1. Preface
  2. Introduction
  3. Getting Started with Repository Manager
  4. Validating Metadata
  5. Promoting Changes Between Repositories
  6. Importing Design Objects
  7. Exporting Repositories
  8. Common Warehouse Model Support
  9. Appendix A: Design Objects Reference
  10. Appendix B: Change List Reference
  11. Appendix C: MetCommand Reference

Hierarchy Manager Requirements

Hierarchy Manager Requirements

Both the source and target repositories must be created in a Informatica MDM Hub environment with identical Hierarchy Manager licensing.
  • You cannot copy changes between repositories if one repository was created in a Informatica MDM Hub environment
    with
    a Hierarchy Manager license if the other was created in a Informatica MDM Hub environment
    without
    a Hierarchy Manager license. The licensing for both environments must be identical—either both had a Hierarchy Manager license, or neither had a hierarchy license.
  • To copy Hierarchy Manager metadata between repositories, both repositories must have been created in a Informatica MDM Hub environment with a Hierarchy Manager license.
In addition to the licensing requirement, Hierarchy Manager for the source and target repositories must be enabled. To enable Hierarchy Manager, open the Hierarchies tool in the Hub Console, select the repository, and follow the prompts to create the Repository Base Objects (RBO tables) and their associated queries and HM packages. For more information, see the
Multidomain MDM Configuration Guide
.
Repository Manager
does not promote, export, or import Repository Base Objects (RBO tables).
Repository Manager
displays a conflict if the source and target ORS databases have RBO tables created in different tablespaces. You should ensure that the source and target RBO tables are created with the same index and data space names.

0 COMMENTS

We’d like to hear from you!