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
  • Data Replication 9.7.0 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

User Guide

User Guide

Back Next

Connecting to an Oracle RAC by Using Custom Connection Strings

Connecting to an Oracle RAC by Using Custom Connection Strings

For Data Replication to support failover in an Oracle RAC, you can define custom connection strings.
Custom connection strings provide connection information for all of the Oracle database instances and ASM instances in the RAC. If the Extractor or the Data Replication Console fails to connect to a particular database or ASM instance, it fails over to another available instance when reconnecting to the database or ASM.
You must provide OCI connection strings for the Extractor and JDBC connection strings for the Data Replication Console in one of the following ways:
  • On the
    Source Database
     tab, click
    New connection
     to create a new source database connection. Then specify the connection strings in the
    New
     dialog box.
  • On the
    Server Manager
     tab >
    Connections
     view, click the
    New
     icon button on the Connections toolbar. Then specify the connection strings in the
    New
     dialog box.
  • On the
    Server Manager
     tab >
    Connections
     view, select an existing Oracle source database connection and click the
    Edit
     icon button on the Connections toolbar. Then specify the connection strings in the
    Editing
     dialog box.
The following steps include sample JDBC and OCI connection strings for a two-node RAC. When you customize the sample connection strings, replace the following variables with actual values:
  • username
    . The Oracle user.
  • password
    . A valid password for the specified user.
  • node1_IP
    . The IP address or host name of the first Oracle instance.
  • node2_IP
    . The IP address or host name of another Oracle instance.
  • port
    . The Oracle listener port. Valid values are integers from 1 through 65535.
  • service_name
    . The Oracle service name. Do not use the database instance name.
  • ASM_service_name
    . The Oracle ASM service name. Do not use the ASM instance name.
The sample connection strings specify two database instances or two ASM instances. If you have an Oracle RAC with more than two instances, add the ADDRESS parameter for each instance in the connection strings.
  1. In the
    New
     or
    Editing
     dialog box for the connection, enter the following connection information for the Oracle database:
    1. In the
      Type
       list, select
      Oracle
      . The database type is already selected for an existing Oracle source database connection.
    2. Select the
      Use Custom URL
       check box.
    3. In the
      JDBC custom URL
       field, enter the JDBC connection string that includes connection information for all database instances.
      For example: 
      jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = 
      node1_IP
      )(PORT = 
      port
      ))(ADDRESS = (PROTOCOL = TCP)(HOST = 
      node2_IP
      )(PORT = 
      port
      ))(LOAD_BALANCE = off)(FAILOVER=on)(CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME = 
      service_name
      )(FAILOVER_MODE =(TYPE = SELECT)(METHOD = preconnect)(RETRIES = 20)(DELAY = 3))))
    4. In the
      Custom Connection String
       field, enter the OCI connection string that includes connection information for all database instances.
      For example: 
      username
      /
      password
      @(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = 
      node1_IP
      )(PORT = 
      port
      ))(ADDRESS = (PROTOCOL = TCP)(HOST = 
      node2_IP
      )(PORT = 
      port
      ))(LOAD_BALANCE = off)(FAILOVER=on)(CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME = 
      service_name
      )(FAILOVER_MODE =(TYPE = SELECT)(METHOD = preconnect)(RETRIES = 20)(DELAY = 3))))
    5. In the
      User
       and
      Password
       fields, enter a database user ID and password for JDBC driver use.
      The Data Replication Console requires the user name and password to connect to the Oracle database because the JDBC connection string does not include this information.
    6. In the
      New
       dialog box, click
      OK
      . In the
      Editing
       dialog box, click
      Save
       and then click
      Yes
       at the confirmation prompt.
  2. On the
    ASM Settings
     tab, enter the following connection information for the Oracle ASM instances:
    1. Select the
      Use custom URL
       option.
    2. In the
      JDBC custom URL
       field, enter the JDBC connection string that includes connection information for all ASM instances.
      For example: 
      jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = 
      node1_IP
      )(PORT = 
      port
      ))(ADDRESS = (PROTOCOL = TCP)(HOST = 
      node2_IP
      )(PORT = 
      port
      ))(LOAD_BALANCE = off)(FAILOVER=on)(CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME = 
      ASM_service_name
      )(UR=A) (FAILOVER_MODE =(TYPE = SELECT)(METHOD = preconnect)(RETRIES = 20)(DELAY = 3))))
    3. In the
      Custom Connection String
       field, enter the OCI connection string for the Oracle ASM instances.
      For example: 
      (DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = 
      node1_IP
      )(PORT = 
      port
      ))(ADDRESS = (PROTOCOL = TCP)(HOST = 
      node2_IP
      )(PORT = 
      port
      ))(LOAD_BALANCE = off)(FAILOVER=on)(CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME = 
      ASM_service_name
      )(UR=A) (FAILOVER_MODE =(TYPE = SELECT)(METHOD = preconnect)(RETRIES = 20)(DELAY = 3))))
      The OCI connection string for Oracle ASM instances does not require a user ID and password.
    4. In the
      ASM sys username
       and
      ASM sys password
       fields, enter an ASM user name and password for JDBC driver use.
      The Data Replication Console requires this user name and password to connect to the Oracle ASM instances because the JDBC connection string does not include this information.
    5. In the
      New
       dialog box, click
      OK
      . In the
      Editing
       dialog box, click
      Save
       and then click
      Yes
       at the confirmation prompt.
0 COMMENTS
We’d like to hear from you!