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

Migrate Databases to IBM DB2 with Oracle-compatibility Disabled

Migrate Databases to IBM DB2 with Oracle-compatibility Disabled

You must migrate databases from the IBM DB2 Oracle-compatibility mode to IBM DB2 with Oracle-compatibility disabled. To migrate a database, extract DDLs and data from the
Hub Store
and update an IBM DB2 instance with Oracle-compatibility disabled. Next, create a
Hub Store
and update it with the extracted DDLs and data.
To migrate an IBM DB2 database in Oracle-compatibility mode to an IBM DB2 database with Oracle-compatibility disabled, perform the following steps:
  1. Create target directories.
  2. Extract
    MDM Hub Master Database
    DDLs and data.
  3. Extract
    Operational Reference Store
    DDLs and data.
  4. Disable the IBM DB2 Oracle-compatibility mode.
  5. Create a Hub Store in the IBM DB2 database with Oracle-compatibility disabled.
  6. Update the
    MDM Hub Master Database
    schema with the extracted source DDLs and data.
  7. Update the
    Operational Reference Store
    schemas with the extracted source DDLs and data.
  8. Ensure that all table constraints reconcile.
  9. Configure the application server to use the IBM DB2 database with Oracle-compatibility disabled.
The database administrative user can be a user other than
db2admin
.

0 COMMENTS

We’d like to hear from you!