Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Appendix B: Frequently Asked Questions

Appendix B: Frequently Asked Questions

Do we need a new license file to upgrade?
Yes. If you are upgrading from a
Multidomain MDM
version 10.1.x or earlier, you need a new license file.
Can we use database user exits from a pre-10.0 version?
No. Database user exits that run in the database layer are deprecated in version 10.0 and later.
Why do we need to provide the DBA username and password during the upgrade process?
The upgrade process performs actions that require DBA-level permissions, such as granting privileges and creating sequences. The DBA credentials are necessary to allow the upgrade process to perform these actions.
What happens to the existing version of ActiveVOS during the upgrade process?
If you have ActiveVOS installed in your environment and you do an in-place upgrade, the upgrade process will install the latest version of ActiveVOS if your environment does not already have it. To see which version of ActiveVOS is required, see the Product Availability Matrix on Informatica Network: https://network.informatica.com/community/informatica-network/product-availability-matrices/overview%20
Is it mandatory to install ActiveVOS during the MDM upgrade process in an environment that does not have ActiveVOS installed?
No. During the upgrade process, you are prompted to choose whether you want to install ActiveVOS.
Has the recommended screen resolution for Informatica Data Director changed in this version?
No, the recommended screen resolution has not changed. The recommended screen resolution for Informatica Data Director is 1280 x 1024.
Do we need to upgrade Informatica Data Quality when we upgrade to
Multidomain MDM
version 10.2 or later?
Yes, if you use Informatica Data Quality (IDQ) in your environment, you must upgrade to version 10.1 of IDQ. For the system requirements, see the Product Availability Matrix on Informatica Network: https://network.informatica.com/community/informatica-network/product-availability-matrices/overview%20
How do we customize MDM Hub security?
For information about customizing MDM Hub security, see the
Multidomain MDM Security Guide
and see the How-to article
Using the Security Configuration Utility in Multidomain MDM
.
Is Java 8 supported?
Yes, this version of
Multidomain MDM
supports Java 8. For the system requirements, see the Product Availability Matrix on Informatica Network: https://network.informatica.com/community/informatica-network/product-availability-matrices/overview%20
ActiveVOS requires Java 7.
If we do not install the Informatica platform, why is the Informatica platform EAR file deployed?
The Informatica platform EAR is deployed to enable the MDM Hub to communicate with the platform. If the Informatica platform is not installed, the EAR file is deployed as a passive application.
If we migrate to use Informatica platform staging, can we set up delta detection, hard delete detection, and audit trails?
By default, Informatica platform staging does not include support for these features. Build your own customization outside the MDM Hub to provide these functions.

0 COMMENTS

We’d like to hear from you!