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. Hierarchies Upgrade
  13. ActiveVOS Post-Installation Tasks for the Application Server
  14. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  15. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  16. Appendix A: Troubleshooting the Upgrade Process
  17. Appendix B: Frequently Asked Questions
  18. Appendix C: Processing Existing ActiveVOS Tasks
  19. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Register the Operational Reference Stores with the Original Schema Owner

Register the Operational Reference Stores with the Original Schema Owner

If any of the Operational Reference Store (ORS) databases are registered with a proxy user, register the ORS database with the original schema owner. You must register the ORS with the original schema owner to ensure that you have sufficient privileges to perform the upgrade operations. You can reregister the ORS with the proxy user after you upgrade. The original default schema owner is CMX_ORS.
  1. Start the Hub Console.
    The
    Change database
    dialog box appears.
  2. Select the MDM Hub Master database, and click
    Connect
    .
  3. Select the
    Databases
    tool from the
    Configuration
    workbench.
  4. Select
    Write Lock
    Acquire Lock
    .
  5. Click the
    Register database
    button.
    The
    Informatica MDM Hub Connection Wizard
    appears and prompts you to select the database type.
  6. Select the type of database, and click
    Next
    .
  7. Configure connection properties for the database.
    1. Select an Oracle connection method, and then click
      Next
      .
      You can select the following Oracle connection methods:
      Service
      Connect to Oracle by using the service name.
      SID
      Connect to Oracle by using the Oracle System ID.
      For more information about SERVICE and SID names, see the Oracle documentation.
      The
      Connection Properties
      page appears.
    2. Specify the connection properties for the connection type that you select, and click
      Next
      .
      You can configure the following connection properties:
      Database Display Name
      Name for the Operational Reference Store that must appear in the Hub Console.
      Machine Identifier
      Prefix given to keys to uniquely identify records from the Hub Store instance.
      Database host name
      IP address or name of the server that hosts the Oracle database.
      SID
      Oracle System Identifier that refers to the instance of the Oracle database running on the server. The
      SID
      field appears if you selected the
      SID
      connection type.
      Service
      Name of the Oracle SERVICE used to connect to the Oracle database. The
      Service
      field appears if the you selected the
      Service
      connection type.
      Port
      The TCP port of the Oracle listener running on the Oracle database server. The default is
      1521
      .
      Oracle TNS Name
      Name by which the database is known on your network as defined in the
      TNSNAMES.ORA
      file of the application server.
      For example:
      mydatabase.mycompany.com
      .
      You set the Oracle TNS name when you install the Oracle database. For more information about the Oracle TNS name, see the Oracle documentation.
      Schema Name
      Name of the Operational Reference Store.
      User name
      Specify the original user name for the ORS. Default is CMX_ORS.
      Password
      Password associated with the original user for the ORS.
      The default password
      ChangeMe
      is displayed as *******, when
      cmx.server.database.authentication.method=windowsauthentication
      in the
      cmxserver.properties
      file. The application will use the Windows authentication to connect to the data source.
      The
      Summary
      page appears.
    3. Review the summary, and specify additional connection properties.
      The following table describes the additional connection properties that you can configure:
      Property
      Description
      Connection URL
      Connect URL. The Connection Wizard generates the connect URL by default. The following list shows the format of the connect URL for the Oracle connection types:
      Service connection type
      jdbc:oracle:thin:@//database_host:port/service_name
      SID connection type
      jdbc:oracle:thin:@//database_host:port:sid
      For a service connection type, you have the option to customize and later test a different connection URL.
      Create datasource after registration
      Select to create the datasource on the application server after registration.
      If you do not select the option, you must manually configure the data source.
    4. For a service connection type, if you want to change the default URL, click the
      Edit
      button, specify the URL, and then click
      OK
      .
  8. Click
    Finish
    .
    The
    Registering Database
    dialog box appears.
  9. Click
    OK
    .
    The MDM Hub registers the ORS.

0 COMMENTS

We’d like to hear from you!