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

Back Next

Enabling Match Population

Enabling Match Population

You must enable the match population to use for the match rules.
  1. Copy the
    <
    population
    >.ysp
     files to the following location:
    On UNIX.
    <
    MDM Hub installation directory
    >/hub/cleanse/resources/match
    On Windows.
    <
    MDM Hub installation directory
    >\hub\cleanse\resources\match
  2. In the C_REPOS_SSA_POPULATION metadata table, verify that the population is registered.
    The seed database for the MDM Hub installation has some populations registered in the C_REPOS_SSA_POPULATION table, but not enabled.
  3. If the C_REPOS_SSA_POPULATION table does not contain the population, add it to the table and enable it.
    The population name is the same as the ysp file name. For example, if the ysp file name is
    US.ysp
    , the population name is US.
    To add the population to an Operational Reference Store, use the following steps:
    On IBM DB2 or Oracle.
    1. Connect to the Operational Reference Store schema that you want to add the population to.
    2. In SQL*Plus, run the
      add_std_ssa_population.sql
       script in the following directory:
      On UNIX.
      <
      MDM Hub installation directory
      >/server/resources/database/custom_scripts/oracle
      On Windows.
      <
      MDM Hub installation directory
      >\server\resources\database\custom_scripts\oracle
    3. Answer the prompts described in the following table:
      Prompt
      Description
      Enter the population to add
      Name of the population.
      Enter a value for ROWID_SSA_POP (example: INFA.0001) DEFAULT [INFA.0001]
      Unique value for the ROWID_SSA_POP column of the C_REPOS_SSA_POPULATION metadata table. Default is
      INFA.0001
      The population is registered in the C_REPOS_SSA_POPULATION table.
    4. Run the following command to enable the population: 
      UPDATE c_repos_ssa_population SET enabled_ind = 1 WHERE population_name = '<
      Your Population
      > ';
COMMIT;
    On Microsoft SQL Server
    1. Run the
      add_std_ssa_population.bat
       script in the following directory:
      <
      MDM Hub installation directory
      >\server\resources\database\custom_scripts\MSSQL
    2. Answer the prompts described in the following table:
      Prompt
      Description
      Hostname with MSSQL instance for CMX_ORS DB ("localhost")
      Host name of the Microsoft SQL Server instance.
      cmx_ors user name ("cmx_ors")
      User name of the Operational Reference Store.
      cmx_ors user password
      Password of the Operational Reference Store.
      Enter the population name (Note: If you use Person_Name_Kanji for the Japan population or Japan_i population, add the suffix '_Kanji' to the end of the name) DEFAULT (" ")
      Name of the population.
      Enter a value for ROWID_SSA_POP (example: INFA.0001) DEFAULT (INFA.0001)
      Unique value for the ROWID_SSA_POP column of the C_REPOS_SSA_POPULATION metadata table.
      The population is registered in the C_REPOS_SSA_POPULATION table.
    3. Run the following command to enable the population: 
      USE <
      Operational Reference Store user
      >
GO
UPDATE [dbo].[C_REPOS_SSA_POPULATION] SET ENABLED_IND = 1 WHERE POPULATION_NAME = '<
      population
      >'
  4. Restart the
    Process Server
    .
  5. Log in to the Hub Console to verify that the population is enabled.
    The population appears in the
    Match/Merge Setup
     user interface for base objects.
0 COMMENTS
We’d like to hear from you!