Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

SharePlex 9.2.4 - Administration Guide

Table of Contents

About this Guide Conventions used in this guide Overview of SharePlex

Advantages of SharePlex About source and target data About SharePlex architecture How SharePlex replication works Understanding the concept of synchronization Strategies for information availability

Run SharePlex on UNIX Run SharePlex on Windows

Run multiple instances of SharePlex

Run multiple instances of SharePlex from separate installations Run multiple instances of SharePlex from one installation

Execute commands in sp_ctrl

How to run sp_ctrl Define a default port for sp_ctrl Define a default host for sp_ctrl Set a default editor for sp_ctrl Command guidelines Issue commands on a remote system Issue commands for a clustered system Add a scroll bar to output on Windows

Set SharePlex parameters

Set and activate parameters Where parameter information is stored

Configure data replication

Ensure compatible source-target mapping Create a configuration file How to qualify object names How to specify case-sensitive names Database specifications in a configuration file Target specifications in a configuration file Routing specifications in a configuration file Configuration examples Capture from multiple local datasources Use Wildcards to specify multiple objects Define a unique key Filter DML operations Map source columns to target columns Build a configuration file using a script

Configure replication to and from a container database

Replicate to and from a PDB

Configure named queues

Configure named export queues Configure named post queues

Configure partitioned replication

Configure horizontally partitioned replication Configure vertically partitioned replication

Configure replication to a change history target

Overview of the change-history target Configure change history

Configure a replication strategy

Configure Replication to share or distribute data Configure Replication to maintain a central data store Configure peer-to-peer replication Configure Replication through an intermediary system Configure Replication to maintain high availability

Configure DDL replication

DDL that SharePlex supports Enable DDL replication Filter DDL Replication Best practices for ALTER TABLE DDL DDL logging and error handling

Configure error handling

Continue to Post when there is an error Continue to Post on DDL errors Increase the number of retries on error Handle transactions that contain out-of-sync operations

Configure data transformation

Overview of transformation Considerations when using transformation Deploy transformation

Configure security features

Secure data with SSL/TLS Host Authentication Secure data with SSH Encrypt data between Export and Import Assign SharePlex users to security groups

Overview of SharePlex security groups Create and populate SharePlex groups on Unix and Linux Create and populate SharePlex groups on Windows

Start replication on your production systems

What is activation? Activation commands Requirements for activating a configuration Test the configuration before activation Frequently Asked Questions about activation How to activate multiple configuration files Activate replication with an Oracle hot backup on an active database Activate replication with an Oracle hot backup on a quiet database Activate replication with Oracle transportable tablespaces Activate replication with cold copy/transfer methods Activate replication from Oracle to Open Target Activate replication from a SQL Server source to any target

Monitor SharePlex

View and kill SharePlex processes View events and errors Monitor with sp_ctrl commands Run monitor scripts on UNIX

Monitor Oracle capture with sp_logmon Monitor events with sp_eventmon Monitor processes with sp_ps Monitor queues with sp_qstatmon

Run a monitor script on Windows Monitor with SNMP

Prevent and solve replication problems

Find the problem in the SharePlex Knowledge Base Solve database setup problems Solve configuration file problems Solve activation problems Solve replication problems Solve Oracle DDL replication problems Solve queue problems Solve synchronization problems Solve compare command errors Solve other problems How to resynchronize source and target objects How to restore Oracle archive logs How to release semaphores after process failure How to resolve disk space shortage How to find the ORACLE_SID and ORACLE_HOME

Repair out-of-sync data

Overview of Compare and Repair Before you use Compare and Repair How to use the repair and compare commands

Tune the Capture process

Disable LOB Mapping Tune Capture on Exadata Tune Checkpointing Add a second thread

Tune the Post process

Use INDEX hints Tune SQL Caching Adjust open cursors Skip maintenance DML Make small transactions faster Split a large transaction into a smaller one Tune queue performance Tune hash-based horizontally partitioned replication

Recover replication after Oracle failover

Recover replication if the primary system fails Recover replication if the secondary Oracle instance fails Move replication during planned failover and failback Resume replication after failure and recovery

Make changes to an active replication environment

Change a configuration file Add or change table specifications in an active replication configuration Change Partitioned Replication Add Oracle sequences to an active replication configuration Remove objects from replication Make DDL changes in an active replication configuration Make Oracle changes that affect replication Change the SharePlex database account Change the name or IP address of a replication host Set the SharePlex port number

Apply an Oracle application patch or upgrade

Before you patch or upgrade an application Apply patch/upgrade to source then copy it to target Apply patch/upgrade to source and target Apply patch to source and replicate it to the target

Back up Oracle data on the source or target

Perform a partial backup of the source system Perform a full backup on the source system

Troubleshooting Tips Appendix A: Peer-To-Peer Diagram Appendix B: SharePlex environment variables

status

Use the status command to view a summary of the status of replication on a system, to ensure that processes are running and to check for errors, warnings or notices. For a more detailed status report, use the lstatus command.

The status display shows:

Process: The name of the process.
State: The status of each process, either running, idle, stopped due to error, or stopped by user
PID: The operating-system process ID number of the process
Running Since: The date and time that the process was started
Other information: such as how the system is being used, if there is an active configuration on the system, and if replication errors occurred.

SharePlex updates the status display at intervals determined by the SP_COP_IDLETIME parameter.

Usage

Supported sources:	Oracle and SQL Server
Supported targets:	All
Authorization level:	Viewer (3)
Issued for:	source or target system
Related commands:	lstatus, qstatus, show, show statusdb

Syntax

Basic command

Remote options

status

[ on host |

on host:portnumber |

on login/password@host |

on login/password@host:portnumber ]

Remote options

These options enable you to issue the command on a remote machine and to script commands that include a login name, password, port number, or combination of those items.

Option	Description
on host	Execute the command on a remote system (one other than the one where the current sp_ctrl session is running). You are prompted for login credentials for the remote system. If used, must be the last component of the command syntax. Example: sp_ctrl(sysB)>status on SysA
on host:portnumber	Execute the command on a remote system when a remote login and port number must be provided. If used, must be the last component of the command syntax. Example: sp_ctrl(sysB)>status on SysA:8304
on login/password@host	Execute the command on a remote system when a remote login, password, and host name must be provided. If used, must be the last component of the command syntax. Example: sp_ctrl(sysB)>status on john/spot5489@SysA
on login/password@host:portnumber	Execute the command on a remote system when a remote login, password, host name, and port number must be provided. If used, must be the last component of the command syntax. Example: sp_ctrl(sysB)>status on john/spot5489@SysA:8304

Related Documents

© 2020 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy