Get Live Help
The following guidelines help you ensure that the source and target objects that you want to map in a replication configuration are compatible.
For most replication strategies, the name and/or owner of a source object can be different from that of its target object. SharePlex replicates to the correct object because you specify it by owner and name within the configuration file. For high-availability configurations, the owner and name of a source table should be the same as the owner and name of the target table.
Corresponding source and target rows must contain the same values to accurately reflect the source, unless transformation is being used.
One database in the configuration can have more or fewer rows than another database in the configuration. You can control which rows are replicated through horizontally partitioned replication. For more information, see Configure horizontally partitioned replication.
Corresponding source and target columns must:
A target table can have more columns than the source table.
A target table can have fewer columns than the number of columns in the source table, but you must use vertically partitioned replication to replicate only that subset of the source columns that matches the rows of the target. For more information, see Configure vertically partitioned replication.
To configure SharePlex to replicate data, you create a configuration file. This is an ASCII text file in which you specify:
Only a SharePlex Administrator or operator has the authority to create a configuration file.
When your configuration file is completed, you activate the configuration with the activate config command to begin replication. For more information, see Activate replication in your production environment.
You can create a configuration file by hand in sp_ctrl or, if your data structure supports it, you can automate the creation of a configuration file with a script.
Create the configuration file on the system from which data is to be replicated, typically the source system, but strategies such as active-active replication require configuration files on more than one system.
To create a configuration file in sp_ctrl
In sp_ctrl, issue the create config command.
sp_ctrl> create config config_name
This command opens a file in the default text editor that is set for the operating system. Note: You can change the default editor that sp_ctrl uses. For more information, see Set a default editor for sp_ctrl.
Complete the configuration file. For more information, see Structure of a configuration file.
Important! All configurations must reside in the config sub-directory of the SharePlex variable-data directory. Configuration files outside this directory cannot be activated. SharePlex places configurations in this directory by default when you create them through the sp_ctrl interface with the create config command. If you create the configuration directly through a text editor, make certain to save it to the config sub-directory.
To build a configuration file with a script
Note: Valid for Oracle only
SharePlex provides the following scripts that can be used to automate the building of your configuration file if the source and target object names are identical. These scripts support Oracle Database source and targets only.
|Option||Description||To get more information|
|config.sql||Builds a configuration file that includes all tables and sequences that are in the database. Source and target object names must be identical.||See Configuration Scripts in the SharePlex Reference Guide.|
|build_config.sql||Builds a configuration file that includes all tables in a schema. Source and target object names must be identical.||See Configuration Scripts in the SharePlex Reference Guide.|
A basic configuration file looks like the following:
# comment: basic SharePlex configuration file
The basic components of a configuration file are as follows.
|# Comments||Lines that describe the file or provide other information about the contents to viewers, but are not used by SharePlex. Precede each comment line with a pound (#) sign. Comments may be entered anywhere in the configuration file.||# This is a comment.|
Syntax that specifies the source database. This component must always be the first non-commented line of a configuration file. It has the following syntax elements, all on the same line with no spaces:
The fully qualified name of a supported source object, in the form of owner.object. The owner can be a schema or a database, depending on how the database stores objects logically. See:
How to specify case-sensitive names
You can use wildcards to specify multiple objects. Owner names cannot be wildcarded. For more information, see Use Wildcards to specify multiple objects.
The target to which the replicated data is applied. Targets supported by SharePlex are:
One or more routes that send the data to the system that contains the target object specified with the target specification. A route consists of the following:
The database specification is absent if the target is JMS, Kafka, or a file.
There can be no spaces between any characters in the routing map.
For more information, see Routing specifications in a configuration file.
Compound routing map:
So that SharePlex can determine the correct objects to capture from, and post to, you must qualify the object names in the configuration file in the same way that the database stores them logically. The general way this is indicated in SharePlex syntax is:
When defining source or target objects in the configuration file, follow these guidelines for specifying the owner component:
|Database||Fully qualified object name|
If the owner (schema or database name) or name of an object is case-sensitive in the database, you must enclose the name within quotes in the SharePlex configuration file.
Note: This applies whether the database itself requires a case-sensitive name to be within quotes, such as Oracle, or whether the database accepts a name that is spelled out in its case-sensitive form without quotes, like SQL Server.
The correct way to specify a fully qualified object name, where both the owner (schema or database) and object components are case-sensitive, is as follows:
The following is not correct, because both components are within one set of quotes:
If only one of the components is case-sensitive, enclose only that name within quotes, and specify the non-case-sensitive name in any case. For example, any of the following is correct:
If a name is not enclosed within quotes in the configuration file, Post converts it to UPPER CASE in its DML operations on the target.