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.
|Activate a configuration file||
Starts the activation and retains control of the sp_ctrl command line until the activation is finished.
|View configuration statistics||
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.
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.
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 and SQL Server source databases, unless otherwise noted.
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.
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.
|Make certain your SharePlex configuration and setup are complete and any optional features are included in the configuration or setup.||Configure SharePlex to replicate data|
Prepare the database to support replication.
|Plan and configure SharePlex to support your replication strategy|
Start the source and target databases.
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.
Before you activate a configuration in production, perform a test activation by using the verify config command. If there are syntax errors, misspellings or duplicate entries in the configuration file, the entire activation will fail.
This command will test the configuration to find and report the following conditions:
The verify config command does not verify how long the activation will take, nor will it verify the target objects or database connection (as represented by the database identifier listed in the routing map.)
For more information, see the verify config command in the SharePlex Reference Guide.
During activation, SharePlex gets the information it needs to identify and understand the objects that are configured for replication and build routing maps. For more information, see What is activation?.
The length of time that activation takes varies, depending on the size, number and structure of the configured objects.
A SQL Server source database must be quiesced (no transaction activity allowed) while a configuration is being activated.
An Oracle database can remain available for transactions. Each source table is briefly locked so SharePlex can build its internal object information. Then the lock is released. This happens very quickly and may not even be noticeable by users. However, if a business application has NOWAIT locking, the SharePlex lock may cause the application to fail if it attempts to obtain a lock on an object that is being activated.
No. The definition of objects cannot be changed during activation.
No. You can create as many configurations for the same source data, but only one of those can be active at the same time.
Yes. This is highly recommended. Use the verify config command. For more information, see Requirements for activating a configuration.
No. Activation is meant to be an uninterrupted procedure that initiates replication while maintaining the same series of transactional events as those appearing in the redo log. You can use the abort config command to terminate an activation, but you may then need to clean out the queues and resynchronize the source and target data again. Ideally, you should have a tested configuration file ready to be activated and be prepared to issue commands to the database and to SharePlex.
Yes. A quiet database is required to activate SQL Server capture, but optional to activate Oracle capture. The Oracle database must be mounted and open, however.
Yes, but only for an Oracle source. The number of threads is controlled globally by the SP_OCF_THREAD_COUNT parameter, which must be set before you issue the activate config command. You can override this value for a particular activation by using the threads option when you issue the activate config command.