Tchater maintenant avec le support
Tchattez avec un ingénieur du support

SharePlex 12.0 - Installation and Setup Guide

About this Guide Conventions used in this guide Installing and Setting up SharePlex on Oracle Source Database
SharePlex Pre-installation Checklist for Oracle Download the SharePlex installer Install SharePlex on Linux and UNIX Set up an Oracle environment for replication Set up replication from Oracle to a different target type Installation and Setup for Cloud-Hosted Databases for Oracle Installation and setup for remote capture Installation and setup for HA cluster Generic SharePlex demonstration for Oracle Advanced SharePlex demonstrations for Oracle Database Setup Utilities Solve Installation Problems for Oracle
Installing and Setting up SharePlex on a PostgreSQL Database as Source and Service
SharePlex Pre-installation Checklist for PostgreSQL Download the SharePlex installer for PostgreSQL Install SharePlex on Linux for PostgreSQL as a Source Set up Replication from PostgreSQL to Supported Target Types Installation and Setup for Cloud-Hosted Databases for PostgreSQL Installation and Setup for Remote Capture for PostgreSQL Install SharePlex on PostgreSQL High Availability Cluster Configure SharePlex on PostgreSQL Azure Flexible Server with High Availability Using Logical Replication Generic SharePlex Demonstration for PostgreSQL Advanced SharePlex Demonstrations for PostgreSQL Database Setup for PostgreSQL Database Setup for PGDB as a Service Installation of pg_hint_plan extension Solve Installation Problems for PostgreSQL
Installing SharePlex on a Docker container Assign SharePlex users to security groups Solve Installation Problems Uninstall SharePlex Advanced installer options Install SharePlex as root SharePlex installed items

Installing and Setting up SharePlex on a PostgreSQL Database as Source and Service

The following installation and setup configurations apply to the PostgreSQL database as a source and service.

Contents

SharePlex Pre-installation Checklist for PostgreSQL

Contents

Review and satisfy all of the requirements in this checklist before installing SharePlex.

Note: The requirements in this checklist apply to all source and target systems where SharePlex will be installed unless otherwise noted.

Network checklist for PostgreSQL

Requirement Completed? (Y/N)

Ensure that SharePlex can resolve host names.

If you find that SharePlex cannot connect to a host, try mapping the host name to an alphanumeric alias in the following locations:

Unix and Linux: Local /etc/hosts file

In these files, put each entry on an individual line. The following is an example, where sysA and sysB are aliases:

111.22.33.44   sysA.company.com   sysA   # source system
55.66.77.88    sysB.company.com   sysB   # target system

 

Verify the SharePlex port number.

By default SharePlex uses the port number 2100 (hex equivalent is 834) for both TCP/IP and UDP. If port 2100 is available to SharePlex, no further action is needed. You will need to enter the SharePlex port number during the installation procedure, at which time you can specify a different port number if needed.

Important! The SharePlex port number must be the same one on all machines in the replication configuration so that they can communicate through TCP/IP connections. Make certain the SharePlex port number is open for TCP/IP on the firewall.

 

Verify TCP/IP settings for PostgreSQL:

SharePlex replicates over any TCP/IP network connection. Typically, if all of the tables in Postgres database are being replicated, SharePlex processes about 54 percent of the WAL file data for replication, the remainder being mostly for internal data used by the Postgres engine for maintenance.

So if WAL file is of 16 MB size (default setting), and all user tables in DB are in replication, then SharePlex will consume approximately 8.6 MB (16 x 0.54) of data for replication.

The following is a formula for determining bandwidth.

(size of a WAL file) x (number of WAL file switches in 1 hour) x 0.54 = volume of data per hour.

For example, if WAL file is of 16 MB in size, and they switch 5 times an hour, SharePlex will process approximately 43.2 MB each hour for replication:

16 x 5 x 0.54 = 43.2 MB/hour

 

Installer checklist for PostgreSQL

Requirement Completed? (Y/N)

Assign a directory to store the downloaded SharePlex installation package.

This directory requires approximately the following disk space:

  • Linux: 200 MB

It can be removed after SharePlex is installed.

 

Plan the SharePlex product directory.

You can create a directory for the SharePlex software files or let the SharePlex installer create it.

This directory requires approximately the following disk space:

  • Linux: 600 MB

Install this directory on the following:

  • Linux: a separate filesystem from the one that contains the database.

Do not install SharePlex on a raw device.

 

Plan the SharePlex variable-data (working) directory

This directory is installed by the SharePlex installer with a name of your choosing. It contains the working data and varies greatly in size in correlation to the volume of data being generated. Install this directory on a separate file system from the one that contains the database, but not on a raw device.

To estimate the required disk space:

  1. Estimate the longest time that a replication outage can be tolerated.
  2. Use the following formula to estimate the amount of data SharePlex would replicate during that amount of time.

    [size of a WAL log] x [number of log switches per hour] x .54 x [number of hoursdowntime] = required disk space

    For example:

    [500 MB WAL log] x [5 switches per hour] x [.54] x [8 hours] = 10.54 GB disk space

To replicate data from more than one database on a system, use a variable-data directory for each one. Ideally they should be on different file systems.

Do not install the variable-data directory within the SharePlex product directory. Both directories contain identically named files, and SharePlex utilities that clean up the environment (if this becomes necessary) could remove the wrong files. You can install both directories under one parent directory if desired.

NOTE: Always monitor disk usage when there is an active SharePlex configuration, especially when there are peaks in transaction activity.

 

Create the SharePlex security groups.

SharePlex provides three security groups to enable access control through sp_ctrl. On Linux, unless you install SharePlex as a root user, the SharePlex Administrator user and the SharePlexPostgreSQL admin group must exist prior to installation. For more information, see Assign SharePlex users to security groups in the SharePlex Admin guide.

Note: If you install as root, you are prompted by the installer to create these groups.

 

Get a valid SharePlex license key.

You must have a valid permanent, term, or trial license key from Quest to run SharePlex. SharePlex licenses have validity and usage limits according to specific platforms. For example, you must have a PostgreSQL license to use a PostgreSQL database and a Kafka license to use the Kafka platform.

Additionally, SharePlex supports multiple keys for situations where customers need two platforms on one server. For example, if a user is replicating data from an Oracle source to a Kafka target, where one SharePlex instance is serving as both the source and target, the SharePlex server would require both Oracle and Kafka licenses.

Note: To install a trial version of SharePlex, users need to select the All Platforms option when prompted during installation of SharePlex or while running the splex_add_key utility.

SharePlex licensing information can be found in the Quest Software Product Guide. Please contact your account manager if you have questions.

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation