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 9.0.1 or 9.1.0 for Oracle

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Hub Store Upgrade Overview

Hub Store Upgrade Overview

The Hub Store is the database that contains the
MDM Hub Master Database
and one or more Operational Reference Store (ORS) databases. Use the scripts provided in the distribution to upgrade the databases.
Before you upgrade, each effective period of a relationship has a dedicated base object record. The upgrade process creates a cross-reference record for each effective period. The upgrade process merges the base object records for each relationship into a single record. The MDM Hub uses the HM_MIG tag in the ROWID_MATCH_RULE column of the HMRG table to track the merged base object records. Do not unmerge these base object records. If you unmerge these relationship base object records, the Hierarchy Manager might display the incorrect effective period for the relationship. Ensure that you assess the impact of the consolidation of hierarchy relationship base objects after the upgrade.
If your database environment is set to a non-English locale, ensure that the character set is a Unicode character set before you upgrade the Hub Store. After the upgrade completes successfully, you can select your preferred locale. The locale is stored as a user account preference, rather than at the database level.
Ensure that you do not include spaces in the path to the database directory or folder names. If you specify a path that has spaces in the directory or folder names, the upgrade fails.

0 COMMENTS

We’d like to hear from you!