지금 지원 담당자와 채팅
지원 담당자와 채팅

SharePlex 11.4 - Installation and Setup guide

About this Guide Conventions used in this guide Revision History Installing and Setting up SharePlex on an Oracle Source
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

Configure, activate, and verify replication on the PostgreSQL source

Note: Before proceeding, make certain the SharePlex demonstration objects are installed.

In this demonstration, you will create and activate a replication configuration, load data to the source table, and then confirm that the data was replicated successfully to the target table. You will also repair a table that is out of synchronization.

Create a configuration file

Note: In this demonstration, the demonstration objects are assumed to be in the schema named demo. Substitute the actual schema, if different.

Perform these steps on the source system:

  1. Run sp_ctrl .

  2. Issue the following command to create a configuration file named sample_config that replicates the sample_department, sample_salary, sample_timesheet, and sample_employee tables to target tables of the same names on the target system..

    sp_ctrl(source)>create config sample_config

  3. In the text editor, build your configuration file based on the following template. Allow no spaces between the characters in a component (source specification, target specification, routing map), and place at least one space between each component.

# sample_config configuration file

datasource:r.source_databasename

"demo"."sample_department"

"demo"."sample_department"

target_system@r.target_databasename

"demo"."sample_salary" "demo"."sample_salary"

target_system@r.target_databasename

"demo"."sample_timesheet" "demo"."sample_timesheet" target_system@r.target_databasename
"demo"."sample_employee" "demo"."sample_employee" target_system@r.target_databasename

where:

  • # denotes a comment.
  • source_databasename is the PostgreSQL database name of the source database.
  • target_system is the name or IP address of the target system.
  • target_databasename is the PostgreSQL database name of the target database.
  1. Save the file, then exit the editor. SharePlex automatically saves the file in the config sub-directory.
  2. In sp_ctrl, verify that the configuration file will activate successfully.

    sp_ctrl(source)>verify config sample_config

Syntax configuration

An example of a config file for PostgreSQL to PostgreSQL replication:

# data2k configuration file

datasource:r.source_databasename

"demo"."data2k" "demo"."data2k" target_system@r.target_databasename

An example of a config file for PostgreSQL to Oracle replication:

# data2k configuration file

datasource:r.source_databasename

"demo"."data2k" "demo"."data2k" target_system@o.target_databasename

Activate the configuration

Perform these steps on the source system. When you activate a configuration, SharePlex is ready to capture transactional changes that are made to the specified source data.

  1. Activate the configuration.

    sp_ctrl(source)>activate config sample_config

    Note: Configuration names are case-sensitive.

  2. Confirm that the configuration activated successfully. The name config sample_config should appear under File Name, and the word Active should appear under State.

    sp_ctrl(source)>list config

Database Setup for PostgreSQL

Pre-requisites to configure PostgreSQL database setup as a source:
  1. In the PostgreSQL configuration file, set the wal_level parameter to logical.
    For example: wal_level = logical # minimal, replica, or logical
  2. Add an entry of SharePlex user in the pg_hba.conf file so that SharePlex Capture can establish a connection with the walsender process of PostgreSQL
    For example: # TYPE DATABASE USER ADDRESS METHOD
    host replication all 10.10.10.10/32 trust
  3. For all the tables which are going to be part of replication, set the 'replica identity' to 'full' before activation.
    For example: alter table "DEMO_SRC" replica identity full;
  4. Navigate to the /var/lib/pgsql/13/data directory and edit the PostgreSQL file.
    Remove the comment and increase the below two parameters' value as below:
    wal_sender_timeout = 6000s
    wal_receiver_timeout = 6000s
  5. Set the value of logical_decoding_work_mem = 4096MB (recommended). This specifies the maximum amount of memory to be used by logical decoding.

  6. Navigate to the bin directory and restart database: cd /usr/pgsql-13/bin/./pg_ctl -D /var/lib/pgsql/13/data/ restart

Notes:

  • The setup steps provided for PostgreSQL are also applicable for setting up SharePlex to replicate data from source/on-prem to a target cloud database.

  • The setup steps provided for PostgreSQL are also applicable for setting up PostgreSQL remote Post.

  • SharePlex PostgreSQL as a source only supports replication from the WAL files present in the pg_wal directory, located within the variable data directory of the PostgreSQL database installation.

  • For controlled character set conversions between source and target, ensure that the PostgreSQL Database character set value and the PGCLIENTENCODING database environment parameter value are exactly the same as those specified in the source and target database character set settings.

Pre-requisites to configure PostgreSQL database setup as a target:

Fujitsu Enterprise PostgreSQL

Fujitsu PostgreSQL contains a customized ODBC driver designed to run with the shared libraries supplied by Fujitsu PostgreSQL. In order to ensure the proper configuration, you must create a symbolic link to ensure that the correct libraries are found at runtime.

Issue Description:

If you attempt to run the pg_setup program prior to creating the symbolic link, pg_setup will fail with the following error message:

Error: [unixODBC]invalid connection option "target_server"

To create a symbolic link:

To ensure that the proper library gets loaded, first locate the path to the directory where the Fujitsu PostgreSQL libraries are installed (for example /opt/fsepv95server64/lib). Then create a symbolic link in the SharePlex OPTDIR/lib/hooks directory pointing to the libpq.so.5 library in the Fujitsu PostgreSQL library directory. For example:

cd /opt/splex/lib/hooks

ln –s /opt/fsepv95server64/lib/libpq.so.5

Overview

Run the PG Setup utility for PostgreSQL (pg_setup) to establish a user account, schema, and tables for use by SharePlex.

Guidelines for use

  • Run the PG Setup utility on PostgreSQL instances in the SharePlex replication configuration.
  • Within a server cluster, run the PG Setup utility on the node to which the shared disk that contains the SharePlex variable-data directory is mounted.
  • For consolidated replication, run the PG Setup utility for each variable-data directory.
  • Provide a DSN (data source name).

    Connection Type on Linux What to do
    DSN

    If you have a DSN defined, and you want to use it for the SharePlex connection, copy or link the ODBC files in which that DSN is defined (odbc.ini and odbcinst.ini) to the odbc subdirectory of the SharePlex variable-data directory. This prevents connection errors when the SharePlex processes connect to the database.

    If you do not have a DSN defined but want to use one, you can create it in the template files provided in the odbc subdirectory.

For an example of the sample odbc.ini and odbcinst.ini files, see the example below:

 

Required Privilege

Review the following requirements to ensure that the setup succeeds.

  • The Database Setup utility must be run as a PostgreSQL Administrator in order to grant SharePlex the required privileges to operate on the database and to create the SharePlex database account.
  • (Symfoware only) If the person who is running the setup utility is not a Fujitsu Enterprise PostgreSQL owner, set the environment variable LD_LIBRARY_PATH to include the path to the lib subdirectory in the Fujitsu Enterprise PostgreSQL installation directory. The LD_LIBRARY_PATH is set in the .bash_profile file of the Fujitsu Enterprise PostgreSQL owner.

    Example:

    export LD_LIBRARY_PATH= /opt/symfoserver64/lib:$LD_LIBRARY_PATH

    If you do not set this path, the following error occurs:

    symbol lookup error: /opt/fsepv95client64/odbc/lib/psqlodbca.so: undefined symbol: PQconnectdbParams

  • Cloud installations:
    • Common restrictions on privileges in cloud-hosted database services make it difficult for the setup utility to succeed in every possible type of scenario. To ensure that the database setup succeeds, only use the setup utility for the following purposes: To do a first-time database setup with a new SharePlex user, or, to modify an existing SharePlex user that either owns the database or has access to it.
    • You might need to grant usage/privileges on the target schema and tables to the SharePlex user, as shown in the following example:

      Log in as the schema owner, then issue the following commands:

      grant usage on schema schema_name to user_name;

      grant all privileges on all tables in schema schema_name to user_name;

    • For Google Cloud database, grant the following privileges if a user wants to change the owner of a table in replication:

      alter user splex_user createdb createrole login;

      create role role_name;

      grant role_name to splex_user;

Run PG setup for PostgreSQL

Follow the below instructions to run the PG setup for PostgreSQL:

  1. Shut down any running SharePlex processes and sp_cop on the source system.
  2. Run the pg_setup program from the bin subdirectory of the SharePlex product directory.

    Important! If you installed the SharePlex instance on any port other than the default of 2100, use the -p option to specify the port number. For example, in the following command the port number is 9400.

    $ /users/splex/bin> pg_setup -p9400

Table 14: Setup prompts and responses

Prompt Response

(Linux)

Enter the PostgreSQL DSN name:

Enter a DSN.
Is DB hosted over "Azure Single Server"?

Enter "n" for a database hosted on the platform other than "Azure single server".

NOTE: Ensure Admin users have the below mentioned roles before initiating setup-

On-Prem DB: superuser

AWS hosted DB: rds_superuser

Azure hosted DB: azure_pg_admin

Enter the PostgreSQL Administrator name :

Enter the name of the PostgreSQL Administrator. This user will perform the work on the SharePlex account.

Enter the password for the Administrator account :

Enter the password of the Administrator.

Enter the database name:

Enter the name of the database that you want to contain the SharePlex tables and other objects for use by SharePlex. You can enter the name of a new or existing database.

Database name database does not exist. Would you like to create it? [y] :

If this prompt is displayed, the specified database does not exist. Press Enter to have the setup utility create it for you.

Would you like to create a new SharePlex user [y]:

Press Enter to accept the default to create a new SharePlex database user account and schema of the same name in the specified database, or enter n to use an existing SharePlex account.

Enter the name of the new SharePlex user:

Enter the name of the existing SharePlex user:

One of these prompts is displayed depending on whether you elected to create a new user or use an existing user. Enter the name of the SharePlex user.

NOTE: Enter the user name in lowercase letters only.

Enter the password of the SharePlex user :

Enter the password of the SharePlex user account.

Re-enter the password for the SharePlex user :

This prompt is only shown if you created a new user. Enter the SharePlex password again.
Will this database be used as a source? [n] :

Enter Y to use the DB connection for a source. You will see the below prompts only for the DB connection for the source.

Enter N to use the DB connection for a target.

Enter the replication slot name? [test_slot] :

Enter the replication slot name.

NOTE: Replication slot test_slot will be created in database after successful config activation.

Enter the default tablespace for use by SharePlex [pg_default] : Enter the default tablespace by SharePlex
Enter the index tablespace for use by SharePlex [pg_default] : Enter the index tablespace by SharePlex
Do you want Logical replication? [n] :

This prompt is displayed only for on-premise hosted PostgreSQL database.

Enter "y" to perform logical replication.

Enter "n" to perform physical replication.

Setup will now install SharePlex objects.

A successful setup terminates with a message similar to the following:

Completed SharePlex for PostgreSQL database configuration

SharePlex User name: splexab

Database name: testdb

-- The datasource identifier in the SharePlex configuration is 'r.testdb' --

 

Important!

Applicable only for source configuration:

SharePlex holds the WAL logs when configuration is not active. In SharePlex 11.0, when pg_setup is executed, it creates a replication slot. From SharePlex 11.1 onwards, slot is created while activating configuration. This replication slot maintains the latest LSN value of the WAL records that Capture has received and processed. Also, it holds all the WAL files from getting removed or archived, starting from the stored LSN in this slot.

In SharePlex 11.1 onwards, the replication slots are dropped while deactivating the configuration.

If SharePlex is shut down without deactivating the config file, then run the pg_cleansp utility to drop the slot. This utility also deletes slot names present in connections.yaml from the installation of version 11.0.

The following steps need to be performed if you do not want to run pg_cleansp:

  1. Get the replication slot name from the var/data/connections.yaml file.

  2. Check if the replication slot exists in the database using the below query:

    select count(*) FROM pg_replication_slots where slot_name = <slot_name>;

  3. If a replication slot exists, then delete that replication slot from the database using the below query:

    select pg_drop_replication_slot(<slot_name>);

  4. If you want to activate the config file, then first execute the pg_setup utility, which will create the replication slot again, and then activate the config file.

Support for hyphen, dot, and plus (-, ., and +) special characters

When the database name contains a hyphen, dot, or plus (-, ., or +) special characters, then remove these characters. Append the _<count> value to the identifier, where the count depends on the datasource identifier existing in the connections.yaml file.

Example:

  • For the database name aaa.db, the datasource identifier will be r.aaadb_1.

  • For the database name aaa+db, the datasource identifier will be r.aaadb_2, as r.aaadb_1 already points to the aaa.db database.

If the database does not contain any special characters but its entry exists in the connections.yaml file, append _<count> to its identifier.

Example:

If the database name is aaadb_1 and its entry exists in the connections.yaml file, and the database name is different, the identifier will become r.aaadb_1_1.

If the database name does not contain a hyphen, dot, or plus character, then the database name is the same as the datasource identifier.

Configure SharePlex to support PostgreSQL database on Azure platform

You can configure SharePlex to support the PostgreSQL database on the Azure platform using the below steps:

  1. Add the DSN entry in the Odbc.ini file at /etc/odbc.ini and the …/var/odbc directory.
  2. Copy the /etc/odbcinst.ini file to the …/var/odbc directory.
  3. Run the PostgreSQL setup utility.
This process creates the SharePlex tables, login and user accounts needed to run SharePlex replication.

Note: While performing DML operations in bulk for PostgreSQL PaaS (Azure), a performance slowness issue is observed.

 

Table 15: Setup Prompts and Responses

Prompt Response

Enter the PostgreSQL DSN name or connection string [] :

Enter the PostgreSQL DSN name or a connection string that connects to the PostgreSQL database system.

Example: pslazpgdb02

Is DB hosted over "Azure Single Server"?

Enter "Y" only when PostgreSQL DB is hosted over 'Azure Single Server'.

Enter the PostgreSQL Administrator name :

Enter the name of the PostgreSQL Administrator. This user will perform the setup work on the SharePlex account and schema.

Example: PostgreSQL

Enter the password for the Administrator account:

Enter the password of the Administrator.

Enter the replication target database name :

Enter the target database name on which replication needs to be performed.

Example: sp_mk

Would you like to create a new SharePlex user?

Enter the name of the existing SharePlex user:

N (If you want to create a user, enter “y”)

 

Enter the name of the SharePlex user.

Enter the password of the SharePlex user:

Enter the password of the SharePlex user account.

Re-enter the password for the SharePlex user:

This prompt is only shown if you created a new user. Enter the SharePlex password again.

A successful setup terminates with a message similar to the following:

Completed SharePlex for PostgreSQL database configuration

SharePlex User name: postgres@pslazpgdb02.postgres.database.azure.com

Database name: sp_mk

The data source identifier in the SharePlex configuration is 'r.sp_mk' –

Database Setup for PGDB as a Service

Database Setup for PostgreSQL Database as a Service

Pre-requisites to configure PostgreSQL database setup as a source:
  1. Modify the cloud database parameters :

    AWS : rds.logical_replication 1

    Azure : wal_level LOGICAL

  2. Add database connection details in the ODBC files in SharePlex var/odbc directory. See the sample screenshot.

  3. For all the tables which are going to be part of replication, set the 'replica identity' to 'full' before activation.
    For example: alter table "DEMO_SRC" replica identity full;

Notes:

  • SharePlex PostgreSQL cloud service as a source only supports logical replication.

  • For controlled character set conversions between source and target, ensure that the PostgreSQL Database character set value and the PGCLIENTENCODING database environment parameter value are exactly the same as those specified in the source and target database character set settings.

Overview

Run the PG Setup utility for PostgreSQL (pg_setup) to establish a user account, schema, and tables for use by SharePlex.

Guidelines for Use

  • Run the PG Setup utility on an independent Linux VM from where the PostgreSQL instance is accessible.
  • For consolidated replication, run the PG Setup utility for each variable-data directory.
  • For PostgreSQL Database as a Service, follow the connection handling best practices recommended by the respective vendor.

  • You can provide a DSN (data source name). Note the following when deciding on the connection method on Linux:

    Connection Type on Linux What to do
    DSN

    If you have a DSN defined, and you want to use it for the SharePlex connection, copy or link the ODBC files in which that DSN is defined (odbc.ini and odbcinst.ini) to the odbc subdirectory of the SharePlex variable-data directory. This prevents connection errors when the SharePlex processes connect to the database.

    If you do not have a DSN defined but want to use one, you can create it in the template files provided in the odbc subdirectory.

For an example of the sample odbc.ini and odbcinst.ini files, see the example below:

 

Required Privilege

Review the following requirements to ensure that the setup succeeds.

  • The Database Setup utility must be run as a PostgreSQL Administrator in order to grant SharePlex the required privileges to operate on the database and to create the SharePlex database account.
  • (Symfoware only) If the person who is running the setup utility is not a Fujitsu Enterprise PostgreSQL owner, set the environment variable LD_LIBRARY_PATH to include the path to the lib subdirectory in the Fujitsu Enterprise PostgreSQL installation directory. The LD_LIBRARY_PATH is set in the .bash_profile file of the Fujitsu Enterprise PostgreSQL owner.

    Example:

    export LD_LIBRARY_PATH= /opt/symfoserver64/lib:$LD_LIBRARY_PATH

    If you do not set this path, the following error occurs:

    symbol lookup error: /opt/fsepv95client64/odbc/lib/psqlodbca.so: undefined symbol: PQconnectdbParams

  • Cloud installations:
    • Common restrictions on privileges in cloud-hosted database services make it difficult for the setup utility to succeed in every possible type of scenario. To ensure that the database setup succeeds, only use the setup utility for the following purposes: To do a first-time database setup with a new SharePlex user, or, to modify an existing SharePlex user that either owns the database or has access to it.
    • You might need to grant usage/privileges on the target schema and tables to the SharePlex user, as shown in the following example:

      Log in as the schema owner, then issue the following commands:

      grant usage on schema schema_name to user_name;

      grant all privileges on all tables in schema schema_name to user_name;

    • For Google Cloud database, grant the following privileges if a user wants to change the owner of a table in replication:

      alter user splex_user createdb createrole login;

      create role role_name;

      grant role_name to splex_user;

Run PG setup for PostgreSQL

Follow the below instructions to run the PG setup for PostgreSQL:

  1. Shut down any running SharePlex processes and sp_cop on the source system.
  2. Run the pg_setup program from the bin subdirectory of the SharePlex product directory.

    Important! If you installed the SharePlex instance on any port other than the default of 2100, use the -p option to specify the port number. For example, in the following command the port number is 9400.

    $ /users/splex/bin> pg_setup -p9400

Table 16: Setup prompts and responses

Prompt Response

Enter the PostgreSQL DSN name:

Enter a DSN.
Is DB hosted over "Azure Single Server"?

Enter "n" for a database hosted on the platform other than "Azure single server".

NOTE: Ensure Admin users have the below mentioned roles before initiating setup-

On-Prem DB:superuser

AWS hosted DB:rds_superuser

Azure hosted DB:azure_pg_admin

Enter the PostgreSQL Administrator name :

Enter the name of the PostgreSQL Administrator. This user will perform the work on the SharePlex account.

Enter the password for the Administrator account :

Enter the password of the Administrator.

Enter the database name:

Enter the name of the database that you want to contain the SharePlex tables and other objects for use by SharePlex. You can enter the name of a new or existing database.

Database name database does not exist. Would you like to create it? [y] :

If this prompt is displayed, the specified database does not exist. Press Enter to have the setup utility create it for you.

Would you like to create a new SharePlex user [y]:

Press Enter to accept the default to create a new SharePlex database user account and schema of the same name in the specified database, or enter n to use an existing SharePlex account.

Enter the name of the new SharePlex user:

Enter the name of the existing SharePlex user:

One of these prompts is displayed depending on whether you elected to create a new user or use an existing user. Enter the name of the SharePlex user.

NOTE: Enter the user name in lowercase letters only.

Enter the password of the SharePlex user :

Enter the password of the SharePlex user account.

Re-enter the password for the SharePlex user :

This prompt is only shown if you created a new user. Enter the SharePlex password again.
Will this database be used as a source? [n] :

Enter Y to use the DB connection for a source. You will see the below prompts only for the DB connection for the source.

Enter N to use the DB connection for a target.

Enter the replication slot name? [test_slot] :

Enter the replication slot name.

NOTE: Replication slot test_slot will be created in database after successful config activation.

Enter the default tablespace for use by SharePlex [pg_default] : Enter the default tablespace by SharePlex
Enter the index tablespace for use by SharePlex [pg_default] : Enter the index tablespace by SharePlex
Do you want Logical replication? [n] :

This prompt is displayed only for on-premise hosted PostgreSQL database.

Enter "y" to perform logical replication.

Enter "n" to perform physical replication.

Setup will now install SharePlex objects.

A successful setup terminates with a message similar to the following:

Completed SharePlex for PostgreSQL database configuration

SharePlex User name: splexab

Database name: testdb

-- The datasource identifier in the SharePlex configuration is 'r.testdb' --

Installation of pg_hint_plan extension

To install pg_hint_plan:

For On-Prem Databases:

  1. Install the RPM according to the PostgreSQL version support matrix at https://github.com/ossc-db/pg_hint_plan.

  2. Run the query with the user [Shareplex user]: CREATE EXTENSION IF NOT EXISTS pg_hint_plan;

  3. Reboot the instance.

For Cloud PostgreSQL:

  1. Set the static parameter in the parameter group: shared_preload_libraries=pg_hint_plan.

  2. Reboot the instance.

NOTE: The total number of background workers that can exist at any one time is limited by both max_worker_processes and max_parallel_workers:

  • max_worker_processes is a database cluster-level parameter and should be set the same as the available CPU vCore.

  • max_parallel_workers is a session-level parameter and should be set less than or equal to max_worker_processes.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택