Infrastructure Planning Guide

10.3 HotFix 1
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3

Back Next

Oracle RAC

The Oracle RAC environment increases performance, improves fault tolerance, and provides scalability. Determine whether your business requires the benefit of using Oracle RAC with the MDM Hub.

For information about Oracle RAC, see the Oracle documentation.

Considerations for using Oracle RAC

Based on the following considerations, decide on the Oracle RAC environment setup:

Use Oracle service names instead of Oracle SIDs for Oracle RAC installations. Provides flexibility to specify the connection and to dynamically reallocate database servers.

Configure all the Oracle RAC nodes in the

tnsnames.ora

file.

Use Oracle RAC load-balanced connections. Distributes the workload among all the available nodes in a cluster. If a node becomes unavailable, the MDM Hub batch job that runs on the node fails. The batch job can be re-triggered and the job will run on one of the available nodes in the cluster.

The MDM Hub supports load balancing for the following operations and components:

Hub Console operations

All batch jobs except the Generate Match Tokens job

The MDM Hub supports load balancing for the fuzzy matching portion of the Match jobs and for the cleanse process portion of the Stage jobs.

Batch jobs cannot use load balancing when called from the Hub Console.

Services Integration Framework (SIF)

Outbound JMS message queues

Hub Server

Process Server

Provisioning tool

Repository Manager

cannot use load balancing when DDL is required because DDL uses a direct JDBC connection.