Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3 HotFix 3
  • All Products

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

Back Next

Step 5. Create a Hub Store

Step 5. Create a Hub Store

The Hub Store comprises an MDM Hub Master Database, and one or more Operational Reference Stores. Use the scripts in the MDM Hub distribution to create the database and associated tablespaces, and the Hub Store.
In IBM DB2 with Oracle-compatibility disabled, create a database, an MDM Hub Master Database, and Operational Reference Stores. After you create the MDM Hub Master Database and Operational Reference Stores, import the seed into them.
  1. Create the database and associated tablespaces.
    1. Change to the following location in the distribution directory:
      On UNIX.
      <
      distribution directory
      >/database/bin
      On Windows.
      <
      distribution directory
      >\database\bin
    2. Run the following command:
      On UNIX.
      sip_ant.sh create_db
      On Windows.
      sip_ant.bat create_db
    3. Answer the prompts described in the following table:
      Prompt
      Description
      Enter the database type (ORACLE, MSSQL, DB2)
      Database type. Specify DB2.
      Enter the database instance name [db2]
      Name of the database instance. Default is
      db2
      .
      Enter the database name [SIP97]
      Name of the database. Default is
      SIP97
      .
      Enter the database storage path [C:\DB2DATA]
      Path to the directory where database must be stored. Default is
      C:\DB2DATA
      .
      On UNIX, accept the default value. The database storage path that you specify in the
      database.properties
       file will be used.
      Enter the DBA user name [DB2ADMIN]
      User name of the administrative user. Default is
      DB2ADMIN
      .
      Enter the DBA password
      Password of the administrative user.
      Create the database proxy role [y/n] [y]
      Specifies whether you want to create the database proxy role.
      Enter one of the following values:
      • y. Creates a database proxy role.
      • n. Database proxy role is not created.
      Default is
      y
      .
      The script creates the database and the required tablespaces.
  2. Create an MDM Hub Master Database.
    1. Change to the following location in the distribution directory:
      On UNIX.
      <
      distribution directory
      >/database/bin
      On Windows.
      <
      distribution directory
      >\database\bin
    2. Run the following command:
      On UNIX.
      sip_ant.sh create_system
      On Windows.
      sip_ant.bat create_system
    3. Answer the prompts described in the following table:
      Prompts
      Description
      Enter the database type (ORACLE, MSSQL, DB2)
      Database type. Specify
      DB2
      .
      Enter the database host name [localhost]
      Name of the host that is running the database. Default is
      localhost
      .
      Enter the database port number [50000]
      Port number that the database listener uses. Default is
      50000
      .
      Enter the database instance name [SIP97]
      Name of the database instance. Default is
      SIP97
      .
      Enter the MDM Hub Master Database schema name [cmx_system]
      Name of the MDM Hub Master Database schema. Defaut is
      cmx_system
      .
      Enter the MDM Hub Master Database user name [cmx_system]
      User name to access the MDM Hub Master Database. Defaut is
      cmx_system
      .
      Enter the MDM Hub Master Database user password
      Password to access the MDM Hub Master Database.
      Enter the DBA user name [DB2ADMIN]
      User name of the administrative user. Default is
      DB2ADMIN
      .
      Enter the DBA password
      Password of the administrative user.
      Use the database proxy role [y/n] [y]
      Specifies whether you want to use the database proxy role that you create when you perform the pre-installation tasks.
      Enter one of the following values:
      • y. Uses the database proxy role.
      • n. Database proxy role is not used.
      Default is
      y
      .
  3. Create an Operational Reference Store.
    1. Change to the following location in the distribution directory:
      On UNIX.
      <
      distribution directory
      >/database/bin
      On Windows.
      <
      distribution directory
      >\database\bin
    2. Run the following command:
      On UNIX.
      sip_ant.sh create_ors
      On Windows.
      sip_ant.bat create_ors
    3. Answer the prompts described in the following table:
      Prompts
      Description
      Enter the database type (ORACLE, MSSQL, DB2)
      Database type. Specify
      DB2
      .
      Enter the Operational Reference Store schema host name [localhost]
      Name of the host that is running the database. Default is
      localhost
      .
      Enter the Operational Reference Store schema port number [50000]
      Port number that the database listener uses. Default is
      50000
      .
      Enter the Operational Reference Store database instance name [SIP97]
      Name of the database instance. Default is
      SIP97
      .
      Enter the Operational Reference Store schema name [cmx_ors]
      Name of the
      Operational Reference Store
       database. Default is
      cmx_ors
      .
      Enter the Operational Reference Store schema user name [cmx_ors]
      User name to access the Operational Reference Store. Default is
      cmx_ors
      .
      Enter the Operational Reference Store schema user password
      Password to access the Operational Reference Store.
      Enter the DBA user name [DB2ADMIN]
      User name of the administrative user. Default is
      DB2ADMIN
      .
      Enter the DBA password
      Password of the administrative user.
      Use the database proxy role [y/n] [y]
      Specifies whether you want to use the database proxy role that you create when you perform the pre-installation tasks.
      Enter one of the following values:
      • y. Uses the database proxy role.
      • n. Database proxy role is not used.
      Default is
      y
      .
  4. Import the seed into the MDM Hub Master Database.
    1. Change to the following location in the distribution directory:
      On UNIX.
      <
      distribution directory
      >/database/bin
      On Windows.
      <
      distribution directory
      >\database\bin
    2. Run the following command:
      On UNIX.
      sip_ant.sh import_system
      On Windows.
      sip_ant.bat import_system
    3. Answer the prompts described in the following table:
      Prompts
      Description
      Enter the database type (ORACLE, MSSQL, DB2)
      Database type. Specify
      DB2
      .
      Enter the database host name [localhost]
      Name of the host that is running the database.
      Enter the database port number [50000]
      Port number that the database listener uses. Default is
      50000
      .
      Enter the database instance name [SIP97]
      Name of the database. Default is
      SIP97
      .
      Enter the MDM Hub Master Database schema name [cmx_system]
      Name of the MDM Hub Master Database schema. Default is
      cmx_system
      .
      Enter the MDM Hub Master Database schema user name [cmx_system]
      User name to access the MDM Hub Master Database. Default is
      cmx_system
      .
      On UNIX, ensure that you use a user name with 8 characters or less.
      Enter the MDM Hub Master Database schema user password
      Password to access the MDM Hub Master Database.
      Enter locale name [en_US]
      Operating system locale. Default is
      en_US
      . Default is
      en_US
      .
      Connect URL [jdbc:db2://localhost:50000/SIP97:currentSchema=CMX_SYSTEM;]
      Connect URL for IBM DB2. Default is
      jdbc:db2://localhost:50000/SIP97:currentSchema=CMX_SYSTEM
      .
      Use the database proxy role [y/n] [y]
      Specifies whether you want to use the database proxy role that you create when you perform the pre-installation tasks.
      Enter one of the following values:
      • y. Uses the database proxy role.
      • n. Database proxy role is not used.
      Default is
      y
      .
  5. Import the seed into the Operational Reference Store.
    1. Change to the following location in the distribution directory:
      On UNIX.
      <
      distribution directory
      >/database/bin
      On Windows.
      <
      distribution directory
      >\database\bin
    2. Run the following command:
      On UNIX.
      sip_ant.sh import_ors
      On Windows.
      sip_ant.bat import_ors
    3. Answer the prompts described in the following table:
      Prompts
      Description
      Enter the database type (ORACLE, MSSQL, DB2)
      Database type. Specify
      DB2
      .
      Enter the Operational Reference Store schema host name [localhost]
      Name of the host that is running the database.
      Enter the Operational Reference Store schema port number [50000]
      Port number that the database listener uses. Default is
      50000
      .
      Enter the database name [SIP97]
      Name of the database. Default is
      SIP97
      .
      Enter the Operational Reference Store schema name [cmx_ors]
      Name of the Operational Reference Store database. Default is
      cmx_ors
      .
      Enter the Operational Reference Store schema user name [cmx_ors]
      User name to access the Operational Reference Store. Default is
      cmx_ors
      .
      Enter the Operational Reference Store schema user password
      Password to access the Operational Reference Store.
      Enter locale name [en_US]
      Operating system locale. Default is
      en_US
      .
      Enter the integer code of Operational Reference Store Timeline Granularity: Year 5, Month 4, Day 3, Hour 2, Minute 1, Second 0 [3]
      Specify timeline units to use. Default is days.
      The timeline granularity that is once configured cannot be modified.
      Use the database proxy role [y/n] [y]
      Specifies whether you want to use the database proxy role that you create when you perform the pre-installation tasks.
      Enter one of the following values:
      • y. Uses the database proxy role.
      • n. Database proxy role is not used.
      Default is
      y
      .
0 COMMENTS
We’d like to hear from you!