Chat now with support
Chat with Support

SharePlex 10.2 - Administration Guide

About this Guide Conventions used in this guide Revision History Overview of SharePlex Run SharePlex Run multiple instances of SharePlex Execute commands in sp_ctrl Set SharePlex parameters Configure data replication Configure replication to and from a container database Configure named queues Configure partitioned replication Configure replication to a change history target Configure a replication strategy Configure DDL replication Configure error handling Configure data transformation Configure security features Start replication on your production systems Monitor SharePlex Prevent and solve replication problems Repair out-of-sync data Tune the Capture process Tune the Post process Recover replication after Oracle failover Make changes to an active replication environment Apply an Oracle application patch or upgrade Back up Oracle data on the source or target Troubleshooting Tips Appendix A: Peer-To-Peer Diagram Appendix B: SharePlex environment variables

Start replication on your production systems

This chapter contains instructions for the initial startup of replication from a source database to a target database on production systems.


What is activation?

When you activate a configuration, through the activate config command in sp_ctrl, SharePlex does the following:

  • Activates (read) the configuration file to build a series of internal structures that identify objects and routes. Only one configuration can be active for any given datasource at a time. Configurations for different datasources on a system can be active at the same time. For example, you can activate a configuration for each Oracle instance.
  • Starts the processes that maintain the capture and replication of source transactions.
  • (Oracle only) Reconciles replicated data with the copied data. SharePlex applies transactions that occurred after the copy was taken and discards transactions that occurred before the copy (and thus were applied by the copy and would be redundant if applied by replication). The reconcile process is only required for procedures that start replication while the source database is active.

The activation of a configuration generally proceeds as follows.

1. Assign an activation ID

SharePlex assigns an activation ID number to each configuration activation and its associated replication processes and queues. A configuration can be activated many times, and this ID keeps track of each one.

2. Create an object cache

SharePlex builds an object cache that records the standard metadata needed to support replication: the name, size, and type of columns, NOT-NULL constraints, and whether a column is part of a key. For tables using partitioned replication, additional information is stored.

3. Add a configuration change marker

SharePlex places a configuration-change marker in the data stream. This marker directs sp_cop to generate a new set of replication processes and queues. If another configuration is active for the same datasource, the marker deactivates it, causing the removal of the old processes and queues after the data they contain is posted.

4. Lock the tables, add the activation marker, unlock

(Oracle only) SharePlex locks the tables that are listed in the configuration file so that it can obtain information about them while they are in a read-consistent state. As many tables can be locked concurrently as there are locking threads available. When SharePlex locks a table, it places an activation marker in the data stream that tells the Capture process to start (or stop) replicating that table.

Note: If an application uses NOWAIT locking on tables in the replication configuration, the NOWAIT could fail if it attempts to obtain a lock on an object that is already locked because it is being activated.

SharePlex locks the following:

  • All tables added to replication (new and reactivated configurations)
  • All tables removed from replication (reactivated configurations)
  • All tables where routes changed (reactivated configurations)

Each table is locked for a very short time, just long enough to activate a table. Replication of each table begins as soon as its activation is complete. Should one or more table fail to activate, SharePlex continues with the activation of the other tables. Users can access the data in a source table when the activation lock is released.

Activation commands

Use sp_ctrl commands to activate, deactivate and view information about a configuration activation, as well as to reconcile ongoing changes with a copy. For more information about these commands, see the SharePlex Reference Guide.

Purpose Command
Activate a configuration file

activate config

Starts the activation and retains control of the sp_ctrl command line until the activation is finished.

View configuration statistics

show config

Shows statistics for active configurations. It displays the status of a configuration (active or inactive), the datasource, the date and time the configuration was activated, and the number of objects that are configured.

Deactivate a configuration file

deactivate config or abort config

The purposes of these commands are different, but both deactivate a configuration file.

  • deactivate config gracefully terminates replication for an active configuration. It stops all Capture activity for the configuration, posts all data currently in the queues, and removes the associated SharePlex processes and queues.
  • abort config is a forceful deactivation. It stops all replication activity for the configured datasource on the source and target systems, whether or not data in the queues has been posted.

Deactivating or aborting a configuration stops replication. If users continue making changes to the configured objects, the source and target data can go out of synchronization.

Reconcile replicated changes with the copy


(Valid for an Oracle source only) Coordinates the results of ongoing replication with a copy of the source data that is applied to the target system, so that changes that occurred before the copy are discarded.

View replication status status

Shows a summary of the status of replication to help you ensure that processes are running and to check for errors, warnings or notices.

View queue status


Shows statistics for the capture, post, and export queues.

Requirements for activating a configuration

Activation of a configuration is an event that requires a series of actions to be taken in a timely manner, uninterrupted. Therefore, it is important to have all of your preparations done ahead of time, leaving nothing in question. You can activate a configuration if you performed the minimal requirements outlined in this topic.

Note: These instructions apply to Oracle source databases, unless otherwise noted.

Required authorization level

Only a SharePlex Administrator can activate a configuration. Additional users should be assigned to monitor SharePlex and perform basic operational procedures. For more information, see Assign SharePlex users to security groups.

Required setup

  • Before you activate a configuration, make certain that the objects that you want to replicate exist in the source database.
  • If a table will be partitioned, create those partitions before you activate a configuration to begin replication processing. Partitioning a table while it is actively replicating causes SharePlex to lose the identifying information it has compiled, and DML from that table partition will not be replicated. You can add a partition to a table already in replication, but you will need to reactivate the configuration to update that table in the SharePlex object cache.


Make certain you satisfy the following prerequisites before you activate a configuration.

Requirement Documentation to Read
Understand how to start and stop the sp_cop program. Run SharePlex

Understand how to issue SharePlex commands.

Execute commands in sp_ctrl

Understand the commands you will use during activation.

Activation commands

Make certain your SharePlex configuration and setup are complete and any optional features are included in the configuration or setup. Configure data replication

Configure partitioned replication

Configure named queues

Configure security features

Configure data transformation

Configure error handling

Prepare the database to support replication.

See "Set up an Oracle environment for replication" in the Installation and Setup Guide for an Oracle Source

Plan and configure SharePlex to support your replication strategy

Configure a replication strategy

Start the source and target databases.

Database documentation

Unless your applications only generate SharePlex-supported DDL, prevent DDL operations, including TRUNCATE, during activation. Where permitted, DML changes are the only permissible changes during activation.

Database documentation
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating