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 2
  • 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

Upgrading the MDM Hub Master Database in Verbose Mode

Upgrading the MDM Hub Master Database in Verbose Mode

To upgrade the
MDM Hub Master Database
, run the upgrade script.
If you did not use the Hub Console to make metadata changes, the database upgrade script might fail. If a script fails, contact Informatica Global Customer Support.
  1. Open a command prompt.
  2. Navigate to the following directory:
    • In UNIX. <
      MDM Hub distribution directory
      >/database/bin
    • In Windows. <
      MDM Hub distribution directory
      >\database\bin
  3. Run the
    MDM Hub Master Database
     upgrade script with the following command:
    • In UNIX.
      sip_ant.sh updatemasterdatabase
    • In Windows.
      sip_ant.bat updatemasterdatabase
  4. Answer the prompts.
    For Oracle environments, provide the following information for the
    MDM Hub Master Database
    :
    Prompt
    Description
    Enter database type (ORACLE, MSSQL, DB2)
    Database type. Specify
    Oracle
    .
    Enter Oracle Connection Type (service, sid). [service]
    Connection type. Use one of the following values:
    SERVICE
    Uses the service name to connect to Oracle.
    SID
    Uses the Oracle System ID to connect to Oracle.
    Default is SERVICE.
    Enter the database host name [localhost]
    Name of the host that is running the database.
    Enter the database port number. [1521]
    Port number that the database listener uses. Default is
    1521
    .
    Enter the database service name [orcl]
    Name of the Oracle service. This prompt appears if the selected Oracle connection type is SERVICE. Default is
    orcl
    .
    Enter Oracle Net connect identifier (TNS Name). [orcl]
    TNS name that is used to connect to the Oracle database. Default is
    orcl
    .
    Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>".
    Connect URL for the Oracle connection type SERVICE.
    Enter database SID [orcl]
    Name of the Oracle System ID. This prompt appears if the selected Oracle connection type is SID.
    Master Database user name [cmx_system]
    You cannot change the MDM Hub Master Database name.
    Enter the Master Database user password
    Password to access the MDM Hub Master Database.
    For IBM DB2 environments, provide the following information for the
    MDM Hub Master Database
    :
    Prompt
    Description
    Enter 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 name [SIP97]
    Name of the database. Default is
    SIP97
    .
    Enter the schema owner user name [DB2ADMIN]
    Name of the owner of the cmx_system schema.
    Enter the schema owner user password.
    Password of the schema owner.
    For Microsoft SQL Server environments, provide the following information for the
    MDM Hub Master Database
    :
    Prompts
    Description
    Enter database type (ORACLE, MSSQL, DB2)
    Database type. Specify
    MSSQL
    .
    Enter the database host name [localhost]
    Name of the host that is running the database.
    Enter the database port number [1433]
    Port number that the database listener uses. Default is
    1433
    .
    Enter the Master Database user password
    Password to access the MDM Hub Master Database.
  5. Answer the following prompt if it appears during the Master Database upgrade: 
    This upgrade should be performed by a DBA to grant ‘create sequence’ privileges for the master database. The master database does not have ‘create sequence’ privileges, you can either grant it now (manually) and then move forward or re-start the upgrade, or direct this process to do so for you now, and continue the current upgrade.
Do you want the process to create this privilege? Yes/No
    • If enter
      No
      , the upgrade process checks again to ensure the user granted the privilege, and then returns to the TNS name prompt.
    • If you enter
      Yes
       , you must answer the following prompts before you can continue with the upgrade process:
      Enter DBA username:
      Enter DBA password:
  6. In JBoss environments, restart the application server.
  7. Save a copy of the CMX_SYSTEM upgrade log files to the upgrade documentation directory. There is a log file for each change script.
    The upgrade process saves the files to the following location:
    • In UNIX. 
      <
      MDM Hub installation directory
      >/server/resources/database/db_changes/<
      database name
      >/Master
    • In Windows. 
      <
      MDM Hub installation directory
      >\server\resources\database\db_changes\<
      database name
      >\Master
0 COMMENTS
We’d like to hear from you!