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

Drop Objects, Columns, and References to Deprecated Objects

Drop Objects, Columns, and References to Deprecated Objects

Upgrade Task
Details
Drop temporary objects created by the readiness check
You can optionally drop the temporary objects that the readiness check creates. Drop the temporary objects to make disk space available.
  1. Navigate to following location:
    • On Windows. <
      MDM Hub installation directory
      >\server\resource\database\migration_readiness\oracle
    • On UNIX. <
      MDM Hub installation directory
      >/server/resource/database/migration_readiness/oracle
  2. In SQL*Plus, run the
    drop_readiness_temp_objects.sql
    script.
Unregister and drop deprecated objects
You can optionally unregister and drop the deprecated HFKM, HMXR, and HUID tables. Unregister and drop the deprecated objects to free up disk space and to avoid
Repository Manager
validation warnings that indicate that deprecated objects exist in the schema.
  1. Resolve any dependencies on the HFKM, HMXR, and HUID tables.
  2. Navigate to the following location:
    • On Windows. <
      MDM Hub installation directory
      >\server\resource\database\migration_readiness\oracle
    • On UNIX. <
      MDM Hub installation directory
      >/server/resource/database/migration_readiness/oracle
  3. In SQL*Plus, run the
    unregister_and_drop_deprecated_objects.sql
    script.
Drop temporary and unusable migration columns
The database migration process creates temporary columns and makes some columns unusable. Drop these columns to free up disk space and increase performance.
  1. Navigate to the following location:
    • On Windows. <
      MDM Hub installation directory
      >\server\resource\database\migration_readiness\oracle
    • On UNIX. <
      MDM Hub installation directory
      >/server/resource/database/migration_readiness/oracle
  2. In SQL*Plus, run the
    drop_unused_columns.sql
    script.
Drop Rel_Start_Date and Rel_End_Date columns
The upgrade process deprecates the Rel_Start_Date and the Rel_End_Date columns as system columns. However, the Rel_Start_Date and the Rel_End_Date columns continue to be available as user columns unless you dropped them from the schema. Drop the Rel_Start_Date and the Rel_End_Date columns for Hierarchy Manager relationship base objects to free up disk space, increase performance, and prevent the columns from being available to users.
To drop the Rel_Start_Date and the Rel_End_Date columns, see the instructions for deleting columns in the
Multidomain MDM Configuration Guide
.
Update references to DIRTY_IND
Update references to the DIRTY_IND system column. The upgrade process replaces the The DIRTY_IND column with a dirty table that is associated with each base object. The dirty table contains the ROWID_OBJECT value of each base object records that needs to be tokenized.
Update references to REL_START_DATE, REL_END_DATE, and HUID tables
Update references to the REL_START_DATE and REL_END_DATE system columns and to the HUID table. The upgrade process removes references to the REL_START_DATE and REL_END_DATE columns in the packages and views used in a Hierarchy Manager base object. Change references from REL_START_DATE to PERIOD_START_DATE. Change references from REL_END_DATE to PERIOD_END_DATE.

0 COMMENTS

We’d like to hear from you!