Chat now with support
Chat with Support

SharePlex 9.0 - Administration Guide

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

Perform a partial backup of the source system

To perform a partial back up of a source system (for example, to extract data or populate a data warehouse) while data is being replicated, you can perform the partial backup on the target system instead and copy the same data as you would on the source system.

This procedure does not interrupt user access to the source data and does not deactivate or reactivate the configuration file.

Supported databases

Oracle or SQL Server source

All targets

Procedure

  1. On the source system, start sp_ctrl.
  2. On the source system, flush the data to the target system. This command stops the Post process and places a marker in the data stream that establishes a synchronization point between source and target data.

    sp_ctrl> flush datasource

    where: datasource is the datasource specification of the source database in the configuration file, for example o.ora1 or r.mss1.

  3. On the target system, back up the data. Note: The data now matches the source data at the flush marker.
  4. On the target system, start the Post process.

    sp_ctrl> start post

Perform a full backup on the source system

To back up the entire source system, including SharePlex, you must shut down SharePlex replication while the backup is performed.

This procedure stops user access to the source data but does not deactivate or reactivate the configuration file. Replication resumes when started after the backup.

Supported databases

Oracle or SQL Server source

All targets

Procedure

Perform these steps on the source system:
  1. Stop all system activity.
  2. Start sp_ctrl.
  3. Flush the data to the target system. This command stops the Post process and places a marker in the data stream that establishes a synchronization point between source and target data.

    sp_ctrl> flush datasource

    where: datasource is the datasource specification of the source database in the configuration file, for example o.ora1 or r.mss1.

  4. Shut down SharePlex. This command shuts down SharePlex.

    sp_ctrl> shutdown

  5. Shut down the database.
  6. Perform the backup.

  7. Start the database.
  8. Start sp_cop (Unix and Linux) or the SharePlex service (Windows).
  9. Start sp_ctrl.
  10. Allow users to access the database.
  11. Verify that the SharePlex Capture, Read, and Export processes started.

    sp_ctrl> status

Perform these steps on the target system:
  1. Start Post.

    sp_ctrl> start post

  2. Verify that Post started.

    sp_ctrl> status

Tune the Capture process

This chapter contains instructions for improving the performance of the Capture process to prevent Capture from losing pace with the volume of redo that an Oracle source database generates.

Contents

Disable LOB Mapping

If you have PK/UK logging enabled on the source database (recommended to support more SharePlex features and faster processing), check the setting of the SP_OCT_ENABLE_LOBMAP parameter. This parameter controls whether or not SharePlex uses a LOB map when replicating tables that contain out-of-row LOB columns. The LOB map is used by the Capture process to map LOBIDs and rows when PK/UK logging is not enabled. LOB mapping is enabled by default. The SHAREPLEX_LOBMAP table stores these mappings.Transactions with numerous LOB operations can slow down Capture because it needs to maintain and refer to the mappings. If PK/UK logging is enabled on the database, you can disable LOB mapping by setting this parameter to 0.

To disable LOB mapping during active replication

  1. Run sp_ctrl on the source system.
  2. Set SP_OCT_ENABLE_LOBMAP to 0.

    sp_ctrl> set param SP_OCT_ENABLE_LOBMAP 0

  3. Stop Capture.

    sp_ctrl> stop capture

  4. Truncate the SHAREPLEX_LOBMAP table.
  5. Restart Capture.

    sp_ctrl> start capture

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating