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.5.1

Upgrading from Version 9.5.1

Back Next

Upgrading Operational Reference Store Databases in Verbose Mode

Upgrading Operational Reference Store Databases in Verbose Mode

To upgrade each Operational Reference Store (ORS) database, run an upgrade script. Upgrade the
MDM Hub Master Database
 before you upgrade the ORS databases.
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. Stop the application server.
  2. Open a command prompt.
  3. Navigate to the following directory:
    • On UNIX. <
      MDM Hub distribution directory
      >/database/bin
    • On Windows. <
      MDM Hub distribution directory
      >\database\bin
  4. Run the Operational Reference Store upgrade script with the following command:
    • UNIX.
      ./sip_ant.sh updateorsdatabase
    • Windows.
      sip_ant.bat updateorsdatabase
  5. Answer the prompts.
    For Oracle environments, provide the following information:
    Prompts
    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 Operational Reference Store database host name [localhost]
    Name of the host that is running the database.
    Enter the Operational Reference Store database port number. [1521]
    Port number that the database listener uses. Default is
    1521
    .
    Enter the Operational Reference Store database service name [orcl]
    Name of the Oracle service. This prompt is displayed if the selected Oracle connection type is SERVICE.
    Enter Oracle Net connect identifier (TNS Name) [orcl]
    Oracle TNS name. Default is
    orcl
    .
    Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/<service_name>".
    Do you want to change the connect URL (y/n) [n]
    Connect URL for the Oracle connection type SERVICE. You can type
    y
     to change the default connect URL. To use the default connect URL, type
    n
    .
    Enter database SID [orcl]
    Name of the Oracle System ID. This prompt is displayed if the selected Oracle connection type is SID.
    Enter the Operational Reference Store database name [cmx_ors]
    Name of the Operational Reference Store database. Default is
    cmx_ors
    .
    Enter the Operational Reference Store database user password
    Password to access the Operational Reference Store.
    Enter locale name from the list: de, en_US, fr, ja, ko, zh_CN. [en_US]
    Operating system locale.
    Enter the DBA username [sys]
    Name of the user with DBA-level permissions.
    Enter the DBA password
    Password of the user with DBA-level permissions.
    Enter integer code of ORS Timeline Granularity: Year 5, Month 4, Day 3, Hour 2, Minute 1, Second 0 [3]
    Specify timeline units to use.
    The upgrade process ignores the value you enter for timeline granularity. You cannot change the timeline granularity that was configured during installation.
    For IBM DB2 environments, provide the following information:
    Prompts
    Description
    Enter database type (ORACLE, MSSQL, DB2)
    Database type. Specify
    DB2
    .
    Enter the Operational Reference Store database host name [localhost]
    Name of the host that is running the database.
    Enter the Operational Reference Store database port number [50000]
    Port number that the database listener uses. Default is 50000.
    Enter the Operational Reference Store database name [SIP97]
    Name of the database. Default is
    SIP97
    .
    Enter the Operational Reference Store database name [cmx_ors]
    Name of the Operational Reference Store database. Default is
    cmx_ors
    .
    Enter the Operational Reference Store database user password
    Password to access the Operational Reference Store.
    Enter locale name from list: de, en_US, fr, ja, ko, zh_CN. [en_US]
    Operating system locale. Default is
    en_US
    .
    Enter the DBA username [sys]
    Name of the user with DBA-level permissions.
    Enter the DBA password
    Password of the user with DBA-level permissions.
    Enter integer code of ORS Timeline Granularity: Year 5, Month 4, Day 3, Hour 2, Minute 1, Second 0 [3]
    Specify timeline units to use.
    The upgrade process ignores the value you enter for timeline granularity. You cannot change the timeline granularity that was configured during installation.
    For Microsoft SQL Server environments, provide the following information:
    Prompts
    Description
    Enter database type (ORACLE, MSSQL, DB2)
    Database type. Specify
    MSSQL
    .
    Enter the Operational Reference Store database host name [localhost]
    Name of the host that is running the database.
    Enter the Operational Reference Store database port number [1433]
    Port number that the database listener uses. Default is
    1433
    .
    Enter the Operational Reference Store database name [cmx_ors]
    Name of the Operational Reference Store database. Default is
    cmx_ors
    .
    Enter the Operational Reference Store database user password
    Password to access the Operational Reference Store.
    Enter locale name from list: de, en_US, fr, ja, ko, zh_CN. [en_US]
    Operating system locale. Default is
    en_US
    .
    Enter the DBA username [sys]
    Name of the user with DBA-level permissions.
    Enter the DBA password
    Password of the user with DBA-level permissions.
    Enter integer code of ORS Timeline Granularity: Year 5, Month 4, Day 3, Hour 2, Minute 1, Second 0 [3]
    Specify timeline units to use.
    The upgrade process ignores the value you enter for timeline granularity. You cannot change the timeline granularity that was configured during installation.
  6. Save a copy of the database debug log the your upgrade documentation directory. The environment report specifies the location of the debug log.
  7. Save a copy of the CMX_ORS 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
      >/ORS
    • In Windows. 
      <
      MDM Hub installation directory
      >\server\resources\database\db_changes\<
      database name
      >\ORS
    The
    sip_ant
     log file is overwritten every time you execute
    sip_ant
     from the command line. You must save a backup copy before you run the
    sip_ant
     script to upgrade another ORS.
0 COMMENTS
We’d like to hear from you!