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

Step 2. Create a Database and Tablespaces

Step 2. Create a Database and Tablespaces

After you install and configure IBM DB2, create and configure databases and tablespaces. You must create a database for each database instance.
If you want to create multiple MDM Hub Master Databases, create unique tablespaces for each MDM Hub Master Database.
The following table describes the tablespaces that you require for the MDM Hub schemas:
Tablespace Name
Description
CMX_DATA
Default tablespace for the Operational Reference Store schema. Contains the metadata and user data of the MDM Hub.
CMX_INDX
Tablespace to contain indexes that the MDM Hub creates and uses.
CMX_TEMP
Tablespace to contain temporary tables that the MDM Hub creates and uses.
CMX_REPOS
Tablespace to contain the Operational Reference Store objects.
CMX_USER_TEMP
Temporary tablespace to contain operational temporary tables.
CMX_SYS_TEMP
Temporary tablespace for SQL operations.
Use one of the following procedures to create a database and tablespaces:
  • Manually create the database and tablespaces
  • Use a script to create the database and tablespaces

0 COMMENTS

We’d like to hear from you!