SharePlex 10.2.1 - Installation and Setup Guide

Configure replication to share or distribute data

These instructions show you how to set up SharePlex for the purpose of sharing or distributing data from one source system to one or more target systems. This strategy supports business requirements such as the following:

• reporting to support real-time decision making
• data sharing to support research and transparency requirements
• data integration throughout an enterprise
• customer service inquiries and other query-intensive applications
• data auditing and archiving

Supported sources

Oracle

Supported targets

All

Capabilities

This replication strategy supports the following:

• Replication to one or more target systems
• Replication between databases on the same system
• Replication between schemas in the same database (Oracle) 
• Identical or different source and target names
• Use of vertically partitioned replication
• Use of horizontally partitioned replication
• Use of named export and post queues
• Use of transformation

Requirements

• Prepare the system, install SharePlex, and configure database accounts according to the instructions in the SharePlex Installation Guide.
• No DML or DDL should be performed on the target tables except by SharePlex. Tables on the target system that are outside the replication configuration can have DML and DDL operations without affecting replication.

• If sequences are unnecessary on the target system, do not replicate them. It can slow down replication. Even if a sequence is used to generate keys in a source table, the sequence values are part of the key columns when the replicated rows are inserted on the target system. The sequence itself does not have to be replicated.

Important! These instructions assume you have a full understanding of SharePlex configuration files. They use abbreviated representations of important syntax elements.

For more information, see Configure data replication.

Conventions used in the syntax

In the configuration syntax in this topic, the placeholders represent the following:

• source_specification[n] is the fully qualified name of a source object (owner.object) or a wildcarded specification.
• target_specification[n] is the fully qualified name of a target object or a wildcarded specification.
• host is the name of a system where SharePlex runs. Different systems are identified by appending a letter to the names, like hostB.
• db is a database specification. The database specification consists of either o. or r. prepended to the Oracle SID, TNS alias, or database name, as appropriate for the connection type. A database identifier is not required if the target is JMS, Kafka, or a file.

Important!

• Configure data replication.

Replicate within the local system

Replication on the same system supports the following configurations:

• Within one Oracle instance, replicate to different tables within the same schema or to the same table in different schemas.
• Replicate to from an Oracle instance to any SharePlex-supported target on the same system.

On the Windows platform, SharePlex does not support replication between Oracle databases that reside on the same system, but you can replicate to Open Target targets on the same system.

Configuration options

Configuration when using SharePlex Manager

Replication from and to the same machine omits an Export process. However, SharePlex Manager expects an export queue to exist. If using this configuration with SharePlex Manager, you must explicitly configure an export queue as follows. The hostA* component in the routing map creates the export queue and an Export process, which sends the data to an Import process, then the post queue.

Replicate to a remote target system

Configuration options

Example

The last line in this example shows how you can replicate data to different target types on the same remote target system.

Replicate to multiple target systems

This topology is known as broadcast replication. It provides the flexibility to distribute different data to different target systems, or all of the data to all of the target systems, or any combination as needed. It assumes the source system can make a direct connection to all of the target systems. All routing is handled through one configuration file.

For more information, see Configure replication through an intermediary system.

Configuration options

If the target specification is identical on all targets

If the target specification of a source object is identical on all target systems, you can use a compound routing map, rather than type a separate entry for each route. For more information, see Configure data replication.

If the target specification is not identical on all targets

• When the target specification of a source object is different on some or all target systems, you must use a separate configuration entry to specify each one that is different.
• You can use a compound routing map for routes where the target specifications are identical.

Example

Note: This example does not cover all possible source-target combinations. The last entry in this example shows the use of horizontally partitioned replication to distribute different data from the sales.accounts table to different regional databases.