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. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.5.1

Upgrading from Version 9.5.1

Prepare for the Upgrade

Prepare for the Upgrade

Perform the following tasks to prepare for the upgrade:
Upgrade Task
Details
Read the Release Notes
The Release Notes contain information about updates to the installation and upgrade process.
Some versions of application servers and databases have known limitations when running
Multidomain MDM
. Ensure that you perform all suggested workarounds.
Read the Release Guide
The Release Guide contains information about new features and changed behavior.
Get the latest license file
Request the latest license file when you request the upgrade software for
Multidomain MDM
.
Review the upgrade restrictions
Review the following conditions before you begin the upgrade:
  • All the components of the
    Multidomain MDM
    implementation must be the same version. If you have multiple versions of
    Multidomain MDM
    , each version must be installed in a separate environment. Different versions of
    Multidomain MDM
    cannot coexist in the same environment.
  • You must not make any major changes to your environment while you upgrade
    Multidomain MDM
    . For example, do not upgrade the Oracle, IBM DB2, or Microsoft SQL Server database during the upgrade process.
  • You must upgrade your Operational Reference Store (ORS) using the upgrade scripts provided. The Repository Manager is not intended to be used as an upgrade tool because some of the artifacts might not be carried over or might be carried over incorrectly from one version to another. For more information, see the
    Multidomain MDM Release Notes
    .
Create an upgrade documentation folder
Create a folder named
upgradedoc
to store copies of all your upgrade artifacts such as metadata validation results, environment reports, and log files. If you encounter problems during the upgrade, you need to send a copy of this directory to Informatica Global Customer Support for analysis.
Review the MDM Hub Environment Report
Use the Enterprise Manager tool in the Hub Console to review the current MDM Hub configuration for Hub Servers, Process Servers, the MDM Hub Master Database, and Operational Reference Store databases. Also note the version history of the components.
Save a copy of the environment report in the upgrade documentation folder.

0 COMMENTS

We’d like to hear from you!