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.7.1

Upgrading from Version 9.7.1

Update the MDM Hub Configuration

Update the MDM Hub Configuration

Perform the following tasks to update the MDM Hub configuration.
Upgrade Task
Details
Grant select right on SYS.V_$PARAMETER for the ORS user
To grant the select right, run the following SQL statement:
grant select on SYS.V_$PARAMETER to <Operational Reference Store user>;
Remove special characters from names in the subject area configuration
You cannot use special characters in names in the Provisioning tool. If you plan to generate a business entity schema from a subject area configuration, you must first remove any special characters from the names in the subject area configuration.
Ensure column names do not contain reserved words
Additional keywords have been marked as reserved in recent versions of
Multidomain MDM
. Ensure you do not use reserved keywords in your implementation.
For a complete list of reserved words, refer to the "Requirements for Defining Schema Objects" section of the
Multidomain MDM Configuration Guide
.
To request a script that changes the name of a column that contains data, contact Informatica Global Customer Support.
Ensure mapped columns have compatible data types
If you use an Oracle database for your Operational Reference Store, check the mappings from landing table to staging table to ensure that the data types of the mapped columns are compatible.
In previous versions, you can create a mapping from a landing table to a staging table where the data types of the mapped columns are not compatible. In this version, the data types of the mapped columns must be compatible. When you load data, if there is a data type mismatch, the load fails with an error in the log files.
For more information about mapping columns, see the
Multidomain MDM Configuration Guide
.
Back up your user preferences from the C_REPOS_DS_PREF table and the C_REPOS_DS_PREF_DETAIL table
If your
Data Director
environment includes user preferences for shown or hidden columns, the settings are lost when you upgrade because the cryptographic hash algorithm has changed in this version. After you upgrade, recreate your user preferences.
For more information about
Data Director
global properties, see the
Multidomain MDM Data Director Implementation Guide
.
Ensure users have a valid email address
Ensure that existing users have valid email addresses associated with their user names in the Hub Console. To reset their passwords to access the MDM Hub, users must have a valid email address.
For more information about editing user information in the Hub Console, see the
Multidomain MDM Security Guide
.
You cannot change the email address for the
admin
user in the Hub Console. To change the email address for the admin user, update the admin user entry directly in the C_REPOS_USER table under CMX_SYSTEM schema.
Register indexes
If you upgrade schemas with custom indexes, you must register the custom indexes. Use the RegisterCustomIndex SIF API to register the custom indexes.
For more information about the RegisterCustomIndex SIF API, see the
Multidomain MDM Services Integration Framework Guide
.

0 COMMENTS

We’d like to hear from you!