This chapter contains the requirements when capturing from a PostgreSQL database and replicating to supported target databases.
This section contains the requirements for a PostgreSQL database as a source when capturing from a PostgreSQL database and replicating to supported target databases.
The following operating systems are supported for capture from a supported PostgreSQL database and replication to supported target database. For a list of supported source and target databases for PostgreSQL capture, see Supported Source and Target Combinations.
SharePlex supports only the 64-bit version of the listed operating systems.
Supported operating systems via native installation
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
PostgreSQL 13.x, 14.x, 15.x, 16
Enterprise Database (EDB) 15.x, 16
Fujitsu Enterprise PostgreSQL 15 SP2
AlloyDB Omni 15.5.x*
*Note: To use the AlloyDB Omni 15.5.x database for data replication using SharePlex, contact the Quest Support team at www.quest.com/contact.
ODBC drivers for Community Edition: postgresql13-odbc-13.02.0000, postgresql14-odbc-13.02.0000,postgresql15-odbc-16.00.0000, and postgresql16-odbc-16.00.0000
ODBC drivers for Enterprise Edition (EDB): edb-odbc-13.02.0000 and edb-odbc-16.00.0000.01
Amazon Web Services:
Amazon EC2 (IaaS) Virtual Machine
Microsoft Azure:
Azure Virtual Machine (IaaS)
Google Cloud Platform:
Cloud SQL for PostgreSQL
AlloyDB for PostgreSQL*
*Note: To use the Google AlloyDB for PostgreSQL Cloud platform for data replication using SharePlex, contact the Quest Support team at www.quest.com/contact.
The following table shows whether specific SharePlex features are supported for replication from PostgreSQL to Oracle and open targets .
| SharePlex feature | Supported targets |
|---|---|
| reconcile command (target instantiation) | Oracle, PostgreSQL |
| compare/compare using and repair/repair using commands | Not supported |
| copy/copy using and append/append using commands | Not supported |
| Hash horizontally partitioned replication | PostgreSQL |
| Column-based horizontally partitioned replication | PostgreSQL |
| Vertically partitioned replication | PostgreSQL, Oracle |
| Column mapping | PostgreSQL, Oracle, SQL Server, Kafka, Snowflake |
| Key definition | PostgreSQL, Oracle |
| Build configuration with scripts | Not supported |
| Named queues | PostgreSQL, Oracle, SQL Server, Kafka, Snowflake |
| Commit Reduction (feature of Post Enhanced Performance) | PostgreSQL, Oracle, SQL Server, Kafka, Snowflake |
| Dependency Checking (feature of Post Enhanced Performance) | Not supported |
| Transformation | Not supported |
| Conflict resolution |
PostgreSQL, Oracle |
| Peer-to-peer replication (bi-directional) | PostgreSQL, Oracle |
| Consolidated replication (many to one) | PostgreSQL, Oracle, SQL Server, Kafka, Snowflake |
| Broadcast replication (one to many) | PostgreSQL, Oracle, SQL Server, Kafka, Snowflake |
| High availability replication (active/passive bi-directional) | Not supported |
| Change tracking target (CDC) | Not supported |
| Data encryption | Not supported |
| Data compression | Not supported |
| SSH | PostgreSQL, Oracle, SQL Server, Kafka, Snowflake |
| auth_hosts file | Not supported |
| Monitoring scripts | Not supported |
| SNMP monitoring | Not supported |
| Continue posting on error (SP_OPX_CONT_ON_ERR) | PostgreSQL, SQL Server, Kafka, Snowflake |
| Suspend on out of sync errors (SP_OPX_OUT_OF_SYNC_SUSPEND) | PostgreSQL, SQL Server, Kafka, Snowflake |
| Reduced key (SP_OPX_REDUCED_KEY) | PostgreSQL, SQL Server, Kafka, Snowflake |
| Logical Transaction Rollback on out-of-sync transactions | Not supported |
| Tables without key* | PostgreSQL, Oracle, SQL Server, Kafka, Snowflake |
* Limitation: Data inconsistency is likely to occur in replication or compare-repair processes when SharePlex replication involves tables containing non-key columns with duplicate data.
The table below presents information on the metrics that are supported and not supported for physical and logical slots in on-premises and PostgreSQL Database as a Service environments.
Note: SharePlex supports logical replication with pgoutput plugin only.
| SharePlex Features | PostgreSQL On-Prem/Cloud VM/EDB (Enterprise Database) | PGDB as a Service AWS- RDS and Aurora, Azure Flexi server | |
|---|---|---|---|
| Physical Replication | Logical Replication (pgoutput plugin) | Logical Replication (pgoutput plugin) | |
| Activate with LSN | Supported | Not supported | Not supported |
| HA Cluster Replication with failover | Applicable with On-prem PostgreSQL database CrunchyData* | Not supported | Applicable only with Azure Flexi server using the pg_failover_slots extension; it is not supported with AWS-RDS and Aurora. |
| Horizontal and Vertical Partitioning | Supported | Supported | Supported |
| Utilities and Commands | Supported | Supported | Supported |
| Database level Table Partitioning | Supported | Supported | Supported |
| Bi-Directional Replication | Supported | Supported | Supported |
| DDL Support | Not supported | Not supported | Not supported |
| Compare and Repair | Not supported | Not supported | Not supported |
| Replication Performance | No Lag | Minimal Lag | Minimal Lag |
| Insert using PostgreSQL Copy command | Not supported | Not supported | Not supported |
* The HA Cluster Replication with Failover feature is not supported with PostgreSQL Enterprise Database (EDB).
SharePlex supports replication from PostgreSQL to Kafka, according to the details below.
Supported operating systems via native installation:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Remote replication from the following operating systems is supported:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Note: SharePlex supports only the 64-bit version of the listed operating systems.
Apache Kafka 0.8.x, 0.9.x, 0.10.x, 0.11.x, 1.0.x, 1.1.x, 2.0.x, 2.1.0, 2.3.1, 2.5.0, 3.0, 3.3, and 3.6.1
We test and reproduce issues against:
Apache Kafka
Confluent Kafka
NOTE: If you would like to use a different vendor who provides their own Kafka distribution or provides a Kafka compliant interface, you are welcome to do so. From a support perspective, our support and development teams will share any Kafka broker errors that SharePlex receives and also ensure SharePlex itself is working properly to capture data, the target configuration formats in SharePlex are correct, and the SharePlex poster is posting or attempting to post according to the Kafka versions under support. If there are SharePlex issues with Kafka support that can be reproduced on Apache Kafka or otherwise demonstrated to be definitely associated with SharePlex, our team will address those as standard Kafka issues.
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL source to a kafka target.
SharePlex supports the following DML operations on tables:
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL source to a Kafka target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL to Oracle, according to the details below.
The following operating systems are supported from PostgreSQL to Oracle database. SharePlex supports only the 64-bit version of the listed operating systems.
Native SharePlex installation is supported on the below platforms:
AIX 7.1, 7.2, and 7.3
Oracle Linux 7.x and 8.x
RHEL 7.x, 8.x, and 9.x
CentOS Linux 7.x
Oracle Solaris SPARC 11
SuSE SLES 12.x and 15.x
HP-UX 11.31 Itanium
Rocky Linux 8.x
Remote replication from the following operating systems is supported:
AIX 7.1, 7.2, and 7.3
Oracle Linux 7.x and 8.x
RHEL 7.x, 8.x, and 9.x
CentOS Linux 7.x
Oracle Solaris SPARC 11
Rocky Linux 8.x
SuSE SLES 12.x and 15.x
HP-UX 11.31 Itanium
Supported target operating systems via remote replication:
All platforms listed above, plus Windows Server 2016 and 2019, are supported via remote replication.
Oracle 19c
Oracle Cloud Infrastructure
Amazon Web Services
Microsoft Azure
Azure Virtual Machine (IaaS)
UTF 8
SharePlex supports the following data types for replication from PostgreSQL to Oracle:
| PostgreSQL | Oracle |
|---|---|
| INT | NUMBER / INT |
| REAL | BINARY_FLOAT / NUMBER |
| SMALLINT | NUMBER |
| BIGINT | NUMBER |
| NUMERIC | NUMBER |
| DOUBLE PRECISION | BINARY_DOUBLE / NUMBER |
| CHAR(1:2000) | CHAR(n) |
| CHAR(2001:) | CLOB |
| CHAR(1:1000) | NCHAR(n) |
| VARCHAR(1:4000) | VARCHAR2(n) |
| VARCHAR(4001:) | CLOB |
| VARCHAR | CLOB |
| VARCHAR(1:2000) | NVARCHAR2(n) |
| TEXT | CLOB / NCLOB |
| DATE | DATE |
| TIMESTAMP(0) | DATE |
| TIMESTAMP(0) | TIMESTAMP(0) |
| TIMESTAMP | TIMESTAMP / TIMESTAMP [(fractional_seconds_precision)] WITH LOCAL TIME ZONE |
| TIMESTAMP WITH TIME ZONE | TIMESTAMP WITH TIME ZONE |
| BOOLEAN | CHAR (1)* |
| BYTEA | BLOB |
*NOTE: For PostgreSQL Physical or Logical replication, BOOLEAN values will be replicated as 1/0 in a CHAR(1) column on the Oracle target.
SharePlex supports the following PostgreSQL data types for replication from PostgreSQL to Oracle when conflict resolution is configured:
VARCHAR
SMALLINT
INT
BIGINT
NUMERIC
DATE
CHAR
TIMESTAMP(0)
TIMESTAMP
TIMESTAMP WITH THE TIME ZONE
TIME
TIME WITH TIME ZONE
BOOLEAN
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL source to an Oracle target.
SharePlex supports the following DML operations on tables:
Singular and bulk operation - Insert
Singular and bulk operation - Update with key(s)/ non key(s)
Singular and bulk operation - Delete with key(s)
Above operations with rollback/savepoint
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL source to an Oracle target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL to PostgreSQL , according to the details below.
Native SharePlex installation is supported on the following platforms:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Remote replication from the following operating systems is supported:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Supported target operating systems via remote replication:
AIX 7.1, 7.2, and 7.3
CentOS Linux 7.x
HP-UX 11.31 Itanium
Oracle Linux 7.x and 8.x
Oracle Solaris SPARC 11.4
Oracle Solaris x86 11.4
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
SuSE SLES 12.x and 15.x
Windows Server 2016 and 2019
Note: SharePlex supports only the 64-bit version of the listed operating systems.
PostgreSQL 13.x, 14.x, 15.x, 16
Enterprise Database (EDB) 15.x, 16
Fujitsu Enterprise PostgreSQL 15 SP2
AlloyDB Omni 15.5.x
Note: To use the AlloyDB Omni 15.5.x database for data replication using SharePlex, contact the Quest Support team at www.quest.com/contact.
ODBC drivers for Community Edition: postgresql13-odbc-13.02.0000, postgresql14-odbc-13.02.0000,postgresql15-odbc-16.00.0000, and postgresql16-odbc-16.00.0000
ODBC drivers for Enterprise Edition (EDB): edb-odbc-13.02.0000 and edb-odbc-16.00.0000.01
Amazon Web Services:
Amazon EC2 (IaaS) Virtual Machine
Amazon RDS for PostgreSQL
Amazon Aurora
Microsoft Azure:
Azure Virtual Machine (IaaS)
Azure DBaaS
Google Cloud Platform:
Cloud SQL for PostgreSQL
AlloyDB for PostgreSQL*
*Note: To use the Google AlloyDB for PostgreSQL Cloud platform for data replication using SharePlex, contact the Quest Support team at www.quest.com/contact.
UTF 8
LATIN1
Note: These character sets are supported only if the same character set is present on both the source and target. For example: Latin1 → Latin1 and UTF8 → UTF8.
SharePlex PostgreSQL supports the following data types for replication from PostgreSQL to PostgreSQL:
|
Limitations:
|
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL source to a PostgreSQL target.
SharePlex supports the following DML operations on tables:
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL source to a PostgreSQL target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL to Snowflake, according to the details below.
The following operating systems are supported for capture from a PostgreSQL database and replication to a Snowflake target database. SharePlex Snowflake supports only the 64-bit version of the listed operating systems.
SharePlex replicates remotely to Snowflake. Replication from the following operating systems is supported:
RHEL 7.x, 8.x, and 9.x
Oracle Linux 7.x and 8.x
Snowflake 6.31 Enterprise, Community version and Snowflake 8.1.0
ODBC driver requirement: Snowflake 3.1.4 and above
Microsoft Azure
SharePlex supports the following data types for replication from PostgreSQL to Snowflake:
| PostgreSQL | Snowflake |
|---|---|
| TEXT | TEXT |
| INT | INT,INTEGER,NUMBER |
| CHAR(1:2000) | VARCHAR(n) |
| CHAR(2001:) | VARCHAR(n) |
| CHAR(n) | CHAR(n) |
| VARCHAR(1:4000) | VARCHAR(n) |
| VARCHAR(4001:) | VARCHAR(n) |
| VARCHAR | VARCHAR(n) |
| REAL | REAL |
| SMALLINT | SMALLINT |
| BIGINT | BIGINT |
| NUMERIC (whole number without fraction) | NUMERIC, DECIMAL |
| NUMERIC (fractional number) | FLOAT |
| DATE | DATE |
| DOUBLE PRECISION | DOUBLE PRECISION |
| TIMESTAMP | TIMESTAMP |
| TIMESTAMP_TZ | TIMESTAMP_TZ |
| BOOLEAN | BOOLEAN |
| TIME | TIME |
Char(n) data type - In PostgreSQL, Char(n) is a fixed-size data type. If you insert char data with a length less than "n" into the "Char(n)" column, the remaining slots (n - length) are padded with space to occupy the complete "n" memory positions. Snowflake uses VARCHAR(n) for char storage since Snowflake lacks a comparable fixed-length character data type and only saves char data up to its length. Live replication will ensure that char column data is correctly copied. However, if users are manually inserting data into Snowflake for the equivalent of a Char(n) PostgreSQL column, then the user will need to handle padding as well to occupy the full "n" length so that data will be in sync in both the source and target database.
Text data types - Snowflake Text data types have size limitation of 8 MB, so PostgreSQL’s TEXT data type replication will be restricted to max 8 MB size limit of equivalent counterpart. Refer table below.
| PostgreSQL Data type | Max Size | Snowflake Data type | Max Size |
|---|---|---|---|
| TEXT | unlimited | TEXT | 8 MB of unicode chars |
SharePlex supports DML operations on tables, with some conditions. DML can be replicated from an PostgreSQL source to a Snowflake target.
SharePlex supports the following DML operations on tables when replicating data from an PostgreSQL source to the Snowflake target:
Singular and bulk operation - Insert with key(s)/ non key(s)
Singular and bulk operation - Update with key(s)/ non key(s)
Singular and bulk operation - Delete with key(s)/ non key(s)
| Limitations:
The following DML operations related limitations are observed while replicating data from PostgreSQL to Snowflake:
|
For additional information, see Supported Operations and Objects for DML Replication.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL source to a Snowflake target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL to SQL Server, according to the details below.
The following operating systems are supported for SQL Server database. SharePlex supports only the 64-bit version of the listed operating systems.
Supported operating systems via native installation:
RHEL 7.x and 8.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Remote replication from the following operating systems is supported:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Supported target operating systems via remote replication:
All platforms listed above, plus Windows Server 2016 and 2019, are supported via remote replication.
SQL Server 2012, 2014, 2016, 2017, 2019, and 2022
Note: SQL Server 2012, 2014, and 2016 databases hosted on Windows servers are compatible with Windows Server 2016 and above.
ODBC driver requirement: ODBC 17.10.1.1-1 and 18.3.2.1-1
Amazon Web Services
Amazon EC2 (IaaS) Virtual Machine
Microsoft Azure
Azure Virtual Machine (IaaS)
Azure SQL Database
Azure SQL Managed Instance
SharePlex supports the following data types for replication from PostgreSQL to SQL Server:
| PostgreSQL | SQL Server |
|---|---|
| INT | INT |
| REAL | REAL |
| SMALLINT | SMALLINT |
| BIGINT | BIGINT |
| NUMERIC / DECIMAL | NUMERIC / DECIMAL |
| DOUBLE PRECISION | FLOAT |
| CHAR (1:8000) | CHAR(n) |
| CHAR (8001:) | VARCHAR (MAX) |
| CHAR (1:2000) | NCHAR (n) |
| VARCHAR (1:8000) | VARCHAR (n) |
| VARCHAR (8001:) | VARCHAR (MAX) |
| VARCHAR(1:2000) | NVARCHAR (n) |
| VARCHAR | VARCHAR (MAX) / TEXT |
| TEXT | TEXT / NTEXT / VARCHAR(MAX) |
| DATE | DATE |
| TIMESTAMP (p) | DATETIME2 (p) |
| TIMESTAMP | DATETIME2 |
| TIMESTAMP WITH TIME ZONE | DATETIMEOFFSET |
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL source to an SQL Server target.
SharePlex supports the following DML operations on tables:
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL source to an SQL Server target. It only supports tables as objects for data replication.
This chapter contains the requirements when capturing from a PostgreSQL database and replicating to supported target databases.
SharePlex supports replication for the PostgreSQL Database as a Service as source, according to the details below.
Supported source operating systems via remote capture:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Supported target operating systems remote replication:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Note: SharePlex supports only the 64-bit version of the listed operating systems.
Amazon Web Services:
Amazon EC2 (IaaS) Virtual Machine
Amazon RDS for PostgreSQL
Amazon Aurora
Microsoft Azure:
Azure Virtual Machine (IaaS)
Azure Database for PostgreSQL Flexible Server
Google Cloud Platform:
Cloud SQL for PostgreSQL
Note: PostgreSQL Database as a Service supports only logical replication.
PostgreSQL 13.x , 14.x, 15.x, 16
ODBC drivers for Community Edition: postgresql13-odbc-13.02.0000, postgresql14-odbc-13.02.0000,postgresql15-odbc-16.00.0000, and postgresql16-odbc-16.00.0000
CHAR
VARCHAR
SMALLINT
INT
BIGINT
NUMERIC
REAL
DOUBLE PRECISION
DATE
TIMESTAMP [p]
TIMESTAMP
TIMESTAMP [p] [WITH TIME ZONE]
TEXT
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service as source to a PostgreSQL target.
SharePlex supports the following DML operations on tables:
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to a PostgreSQL target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL Database as a Service to Kafka, according to the details below.
Supported source operating systems via remote capture:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Remote replication from the following operating systems is supported:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Note: SharePlex supports only the 64-bit version of the listed operating systems.
Apache Kafka 0.8.x, 0.9.x, 0.10.x, 0.11.x, 1.0.x, 1.1.x, 2.0.x, 2.1.0, 2.3.1, 2.5.0, 3.0, 3.3, and 3.6.1
We test and reproduce issues against:
Apache Kafka
Confluent Kafka
NOTE: If you would like to use a different vendor who provides their own Kafka distribution or provides a Kafka compliant interface, you are welcome to do so. From a support perspective, our support and development teams will share any Kafka broker errors that SharePlex receives and also ensure SharePlex itself is working properly to capture data, the target configuration formats in SharePlex are correct, and the SharePlex poster is posting or attempting to post according to the Kafka versions under support. If there are SharePlex issues with Kafka support that can be reproduced on Apache Kafka or otherwise demonstrated to be definitely associated with SharePlex, our team will address those as standard Kafka issues.
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service as source to a Kafka target.
SharePlex supports the following DML operations on tables:
SharePlex does not support DDL operations and objects when replicating data from a PostgreSQL Database as a Service as source to a Kafka target.
SharePlex supports replication from PostgreSQL Database as a Service to Oracle, according to the details below.
The following operating systems are supported from PostgreSQL Database as a Service to Oracle database. SharePlex supports only the 64-bit version of the listed operating systems.
Native SharePlex installation is supported on the below platforms:
AIX 7.1, 7.2, and 7.3
Oracle Linux 7.x and 8.x
RHEL 7.x, 8.x, and 9.x
CentOS Linux 7.x
Oracle Solaris SPARC 11
Rocky Linux 8.x
SuSE SLES 12.x and 15.x
HP-UX 11.31 Itanium
Remote replication from the following operating systems is supported:
AIX 7.1, 7.2, and 7.3
Oracle Linux 7.x and 8.x
RHEL 7.x, 8.x, and 9.x
CentOS Linux 7.x
Oracle Solaris SPARC 11
Rocky Linux 8.x
SuSE SLES 12.x and 15.x
HP-UX 11.31 Itanium
Supported target operating systems via remote replication:
All platforms listed above, plus Windows Server 2016 and 2019, are supported via remote replication.
Oracle 19c
Oracle Cloud Infrastructure
Amazon Web Services
Microsoft Azure
Azure Virtual Machine (IaaS)
UTF 8
SharePlex supports the following data types for replication from PostgreSQL Database as a Service to Oracle:
| PostgreSQL | Oracle |
|---|---|
| INT | NUMBER / INT |
| REAL | BINARY_FLOAT / NUMBER |
| SMALLINT | NUMBER |
| BIGINT | NUMBER |
| NUMERIC | NUMBER |
| DOUBLE PRECISION | BINARY_DOUBLE / NUMBER |
| CHAR(1:2000) | CHAR(n) |
| CHAR(2001:) | CLOB |
| CHAR(1:1000) | NCHAR(n) |
| VARCHAR(1:4000) | VARCHAR2(n) |
| VARCHAR(4001:) | CLOB |
| VARCHAR | CLOB |
| VARCHAR(1:2000) | NVARCHAR2(n) |
| TEXT | CLOB / NCLOB |
| DATE | DATE |
| TIMESTAMP(0) | DATE |
| TIMESTAMP(0) | TIMESTAMP(0) |
| TIMESTAMP | TIMESTAMP / TIMESTAMP [(fractional_seconds_precision)] WITH LOCAL TIME ZONE |
| TIMESTAMP WITH TIME ZONE | TIMESTAMP WITH TIME ZONE |
| BOOLEAN | CHAR (1)* |
| BYTEA | BLOB |
*NOTE: For PostgreSQL Physical or Logical replication, BOOLEAN values will be replicated as 1/0 in a CHAR(1) column on the Oracle target.
SharePlex supports the following PostgreSQL data types for replication from PostgreSQL Database as a Service to Oracle when conflict resolution is configured:
VARCHAR
SMALLINT
INT
BIGINT
NUMERIC
DATE
CHAR
TIMESTAMP(0)
TIMESTAMP
TIMESTAMP WITH THE TIME ZONE
TIME
TIME WITH TIME ZONE
BOOLEAN
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service to an Oracle target.
SharePlex supports the following DML operations on tables:
Singular and bulk operation - Insert
Singular and bulk operation - Update with key(s)/ non key(s)
Singular and bulk operation - Delete with key(s)
Above operations with rollback/savepoint
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to an Oracle target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL Database as a Service to PostgreSQL, according to the details below.
Native SharePlex installation is supported on the following platforms:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Remote replication from the following operating systems is supported:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Supported target operating systems via remote replication:
AIX 7.1, 7.2, and 7.3
CentOS Linux 7.x
HP-UX 11.31 Itanium
Oracle Linux 7.x and 8.x
Oracle Solaris SPARC 11.4
Oracle Solaris x86 11.4
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
SuSE SLES 12.x and 15.x
Windows Server 2016 and 2019
Note: SharePlex supports only the 64-bit version of the listed operating systems.
PostgreSQL 13.x , 14.x, 15.x, 16
Enterprise Database (EDB) 15.x and 16
Fujitsu Enterprise PostgreSQL 15 SP2
AlloyDB Omni 15.5.x*
*Note: To use the AlloyDB Omni 15.5.x database for data replication using SharePlex, contact the Quest Support team at www.quest.com/contact.
ODBC drivers for Community Edition: postgresql13-odbc-13.02.0000, postgresql14-odbc-13.02.0000,postgresql15-odbc-16.00.0000, and postgresql16-odbc-16.00.0000
ODBC drivers for Enterprise Edition (EDB): edb-odbc-13.02.0000 and edb-odbc-16.00.0000.01
Amazon Web Services:
Amazon EC2 (IaaS) Virtual Machine
Amazon RDS for PostgreSQL
Amazon Aurora
Microsoft Azure:
Azure Virtual Machine (IaaS)
Azure DBaaS
Google Cloud Platform:
Cloud SQL for PostgreSQL
AlloyDB for PostgreSQL*
*Note: To use the Google AlloyDB for PostgreSQL Cloud platform for data replication using SharePlex, contact the Quest Support team at www.quest.com/contact.
UTF 8
LATIN1
Note: These character sets are supported only if the same character set is present on both the source and target. For example: Latin1 → Latin1 and UTF8 → UTF8.
SharePlex PostgreSQL supports the following data types for replication from PostgreSQL Database as a Service to PostgreSQL:
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service to a PostgreSQL target.
SharePlex supports the following DML operations on tables:
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to a PostgreSQL target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL Database as a Service to Snowflake, according to the details below.
The following operating systems are supported for capture from a PostgreSQL Database as a Service and replication to a Snowflake target database. SharePlex Snowflake supports only the 64-bit version of the listed operating systems.
SharePlex replicates remotely to Snowflake. Replication from the following operating systems is supported:
RHEL 7.x, 8.x, and 9.x
Oracle Linux 7.x and 8.x
Snowflake 6.31 Enterprise, Community version, and Snowflake 8.1.0
ODBC driver requirement: Snowflake 3.1.4 and above
Microsoft Azure
SharePlex supports the following data types for replication from PostgreSQL Database as a Service to Snowflake:
| PostgreSQL | Snowflake |
|---|---|
| TEXT | TEXT |
| INT | INT,INTEGER,NUMBER |
| CHAR(1:2000) | VARCHAR(n) |
| CHAR(2001:) | VARCHAR(n) |
| CHAR(n) | CHAR(n) |
| VARCHAR(1:4000) | VARCHAR(n) |
| VARCHAR(4001:) | VARCHAR(n) |
| VARCHAR | VARCHAR(n) |
| REAL | REAL |
| SMALLINT | SMALLINT |
| BIGINT | BIGINT |
| NUMERIC (whole number without fraction) | NUMERIC, DECIMAL |
| NUMERIC (fractional number) | FLOAT |
| DATE | DATE |
| DOUBLE PRECISION | DOUBLE PRECISION |
| TIMESTAMP | TIMESTAMP |
| TIMESTAMP_TZ | TIMESTAMP_TZ |
| BOOLEAN | BOOLEAN |
| TIME | TIME |
Char(n) data type - In PostgreSQL, Char(n) is a fixed-size data type. If you insert char data with a length less than "n" into the "Char(n)" column, the remaining slots (n - length) are padded with space to occupy the complete "n" memory positions. Snowflake uses VARCHAR(n) for char storage since Snowflake lacks a comparable fixed-length character data type and only saves char data up to its length. Live replication will ensure that char column data is correctly copied. However, if users are manually inserting data into Snowflake for the equivalent of a Char(n) PostgreSQL column, then the user will need to handle padding as well to occupy the full "n" length so that data will be in sync in both the source and target database.
Text data types - Snowflake Text data types have size limitation of 8 MB, so PostgreSQL’s TEXT data type replication will be restricted to max 8 MB size limit of equivalent counterpart. Refer table below.
| PostgreSQL Data type | Max Size | Snowflake Data type | Max Size |
|---|---|---|---|
| TEXT | unlimited | TEXT | 8 MB of unicode chars |
See Conditions of support for the additional conditions of support for the above-mentioned supported data types.
SharePlex supports DML operations on tables, with some conditions. DML can be replicated from an PostgreSQL Database as a Service to a Snowflake target.
SharePlex supports the following DML operations on tables when replicating data from an PostgreSQL Database as a Service to the Snowflake target:
Singular and bulk operation - Insert with key(s)/ non key(s)
Singular and bulk operation - Update with key(s)/ non key(s)
Singular and bulk operation - Delete with key(s)/ non key(s)
| Limitations:
The following DML operations related limitations are observed while replicating data from PostgreSQL Database as a Service to Snowflake:
|
For additional information, see Supported Operations and Objects for DML Replication.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to a Snowflake target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL Database as a Service to SQL Server, according to the details below.
The following operating systems are supported for SQL Server database. SharePlex supports only the 64-bit version of the listed operating systems.
Supported operating systems via native installation:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Remote replication from the following operating systems is supported:
RHEL 7.x, 8.x, and 9.x
Rocky Linux 8.x
Oracle Linux 7.x and 8.x
Supported target operating systems via remote replication:
All platforms listed above, plus Windows Server 2016 and 2019, are supported via remote replication.
SQL Server 2012, 2014, 2016, 2017, 2019 and 2022
Note: SQL Server 2012, 2014, and 2016 databases hosted on Windows servers are compatible with Windows Server 2016 and above.
ODBC driver requirement: ODBC 17.10.1.1-1 and 18.3.2.1-1
Amazon Web Services
Amazon EC2 (IaaS) Virtual Machine
Microsoft Azure
Azure Virtual Machine (IaaS)
Azure SQL Database
Azure SQL Managed Instance
SharePlex supports the following data types for replication from PostgreSQL Database as a Service to SQL Server:
| PostgreSQL | SQL Server |
|---|---|
| INT | INT |
| REAL | REAL |
| SMALLINT | SMALLINT |
| BIGINT | BIGINT |
| NUMERIC / DECIMAL | NUMERIC / DECIMAL |
| DOUBLE PRECISION | FLOAT |
| CHAR (1:8000) | CHAR(n) |
| CHAR (8001:) | VARCHAR (MAX) |
| CHAR (1:2000) | NCHAR (n) |
| VARCHAR (1:8000) | VARCHAR (n) |
| VARCHAR (8001:) | VARCHAR (MAX) |
| VARCHAR(1:2000) | NVARCHAR (n) |
| VARCHAR | VARCHAR (MAX) / TEXT |
| TEXT | TEXT / NTEXT / VARCHAR(MAX) |
| DATE | DATE |
| TIMESTAMP (p) | DATETIME2 (p) |
| TIMESTAMP | DATETIME2 |
| TIMESTAMP WITH TIME ZONE | DATETIMEOFFSET |
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service to an SQL Server target.
SharePlex supports the following DML operations on tables:
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to an SQL Server target. It only supports tables as objects for data replication.
The following is a list of known issues, including those attributed to third-party products, known to exist at the time of release.
| Issue ID | Known Issues | Component/ Feature |
|---|---|---|
| SPO-24922 | SharePlex does not support the RAISE command on PostgreSQL databases. Poster stops with the Post stops error=-1 when trigger issues a RAISE [LABEL] error message. | RAISE command |
| SPSQL-2530 | Performance issues are observed during bulk DML operations on the text data type in a PostgreSQL cloud database (PGDBaaS). | PGDBaaS |
| SPSQL-7057 |
The Compare process displays an error while comparing the table during replication in SharePlex version 11.4. This issue is observed after upgrading SharePlex from version 11.x to 11.4. Workaround: After upgrading, to bring up your existing setup, activate the same configuration file again if your source is PostgreSQL with logical replication. This will add newly created SharePlex internal tables to the publication used for logical replication before starting the Capture process. |
Upgrade |
| SPSQL-7046 | SharePlex fails to replicate bulk data from Oracle to Snowflake when table or column names are case-sensitive. | Bulk update |
| SPSQL-6609 | SharePlex displays an error when users attempt to create a database name in lowercase during pg_setup that matches an existing database name in uppercase on the system. | pg_setup |
| SPSQL-6104 | The SharePlex Poster process stopped due to an ORA-40441 error: JSON syntax error, triggered when users insert bulk JSON data for CLOB/NCLOB storage, which is stored as BASICFILE. | Poster |
| SPSQL-5625 | SharePlex displays the "Error encountered in remove_trigger objectid" error when users attempt to disable or enable any trigger using the sp_pg_add_trigger.sql and sp_pg_remove_trigger.sql scripts for the given schema. | Trigger Scripts |
| SPSQL-5252 |
In the bi-directional replication of data from PostgreSQL 14.7 Google Cloud Platform to Oracle, the Poster process stops with an error when a user-defined procedure tries to resolve the conflicts that occurred on columns with a VARCHAR data type. This issue is observed if the update statement is triggered simultaneously in the same row on both source and target. |
Bi-directional replication |
| SPO-24085 | The SharePlex Poster process is performing slow after upgrading to version 10.1.3. | Poster |
| SPSQL-4982 | When there are multiple Named Queues set up in replication, after activating the config, the SharePlex Poster process displays the execute select pg_replication_origin_create ('sp_post_2600_7'); failed error upon its initial startup. However, after displaying the error, SharePlex automatically restarts the Poster process to resolve the issue. | Poster |
| SPSQL-6502 | The SharePlex Poster process is stopping due to the Poster stopped due to error: missing column on target table error during a DML operation. This issue is observed with the latest versions of MySQL and the ODBC driver. This issue is observed while replicating data from Oracle to MySQL. | Poster |
| SPSQL-4971 | The tables are getting out-of-sync after users perform bulk DML operations on the CLOB column data. This issue has been observed while working on Oracle 21c. | Oracle 21c |
| SPSQL-4854 |
The SharePlex Poster displays an error regarding the invalid length for a variable character string while replicating CLOB column data from Oracle to Oracle. This issue has been observed while working on Oracle 19c on the RHEL platform, Oracle 21c. Affected versions: SharePlex 10.2, 11.0, 11.1, and 11.2 on the Linux platform. |
Oracle to Oracle |
| SPSQL-4909 | SharePlex displays a value in the TARGET_ROWID column of the shareplex_conf_log table even when the user sets the parameter SP_OPO_LOG_CONFLICT to 1. This issue is observed while replicating data from PostgreSQL to Oracle and Oracle to Oracle. | PostgreSQL to Oracle and Oracle to Oracle. |
| SPSQL-3596 | In bi-directional replication of data from PostgreSQL to Oracle, an Oracle custom routine (splex.PROCEDURE1) is not taking priority over a SharePlex-prepared routine. On the contrary, the SharePlex-prepared routine (LeastRecentRecord) is taking priority over the custom procedure on Oracle Peer for conflict resolution. | PostgreSQL-Oracle BDR |
| SPSQL-6618 | The SharePlex Compare process fails with an error while comparing tables using wild card data in the command options for o.sid/r.dbid. This issue is observed while replicating data from Oracle to Oracle and PostgreSQL to PostgreSQL. | Compare |
| SPSQL-6608 | The SharePlex Compare process fails with Error: RouteDB.load routes file does not exist for actid when comparing data containing special characters using the config file. This issue is observed while replicating data from PostgreSQL to PostgreSQL. | Compare |
| SPSQL-6607 | SharePlex is displaying an error when executing a Compare/Repair query command with wildcards for multiple tables that have a different number of columns. This issue is observed while replicating data from PostgreSQL to PostgreSQL. | Compare/Repair |
| SPO-24757 |
SharePlex displays the “ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT” error while performing the Compare/Repair operation on the XML data. Workaround:
WITH MAX_PGA as (select round(value/1024/1024,1) max_pga from v$pgastat where name='maximum PGA allocated'), MGA_CURR as (select round(value/1024/1024,1) mga_curr from v$pgastat where name='MGA allocated (under PGA)'), MAX_UTIL as (select max_utilization as max_util from v$resource_limit where resource_name='processes') SELECT a.max_pga "Max PGA (MB)", b.mga_curr "Current MGA (MB)", c.max_util "Max # of processes", round(((a.max_pga - b.mga_curr) + (c.max_util * 5)) * 1.1, 1) "New PGA_AGGREGATE_LIMIT (MB)" FROM MAX_PGA a, MGA_CURR b, MAX_UTIL c WHERE 1 = 1;
|
Compare/Repair |
| SPO-22342 | Performance issue is observed while performing the DML operations in bulk. | MySQL |
| SPO-22517 | Performance issue is observed during replication while using partition table over the cloud. | PostgreSQL and MySQL |
| SPO-21993 | While activating a config file with an Oracle SCN number, users are not able to delete a column in a DDL activity. | DDL Drop Column |
| SPO-21339 | The SharePlex Capture process is getting stuck when users change the Oracle compatibility parameter from 11g to 12c. This issue is observed on the 12c 4 node RAC database. | Capture |
| SPO-20843 | Copy job status shows 'Locked' even when competed. | Copy/ Append |
| SPO-20842 | On Oracle 19c processing large n-items can lead to OOS and/or missing commits. | LOBs, VARRAYs, XML |
| SPO-20841 | Post will fail with ORA-14400 performing DML on partitioned table with VARRAY residing in an OLTP compressed table space. | Partitioned Replication |
| SPO-20733 | Compare will hang and the compare server will exit comparing table that has VARRAY containing UDT type. | Compare |
| SPO-20451 | Compare/Repair using [schema].[table] may not work on AIX 7.2 with Oracle 19c due to establishing a network connection. | Compare |
| SPO-20205 | Oracle to Kafka supported data format: Kafka replicates the varray column data only in the XML format. Currently, Kafka does not replicate the varray column data in the JSON format. |
Kafka |
| SPO-19048 | Replication of tables with varray columns from an Oracle source to a non-Oracle target can get out of sync because Oracle doesn't include key information on updates. | Post to non-Oracle targets |
| SPO-16453 | The BINARY_FLOAT and BINARY_DOUBLE data types are not supported for the copy command. | Character Sets |
| SPO-22429 | SharePlex is displaying the 'ERROR: invalid byte sequence for encoding "UTF8": 0xfd;' error related to character mapping while replicating data from an Oracle database to a PostgreSQL database. | Character Mapping |
| Issue ID | Known Issue | Component/ Feature |
|---|---|---|
| SR 3-33906406631 | After moving the LOB segment, users may encounter an 'ORA-22275' or 'ORA-22990' Oracle error when performing DML operations. Additionally, the Compare result may be displayed as out of sync. This issue is observed intermittently on Oracle 21c. See Oracle bug report SR 3-33906406631. | Oracle |
| 101806 | When replicating data from Oracle to MySQL, SharePlex Poster displays an error after performing the Update operation on columns with the data type integer and column values that are multiples of 1000. This issue is related to a defect in the MySQL database: https://bugs.mysql.com/bug.php?id=101806 | MySQL |
| 54799 | RHEL with 11g may encounter issues when producing core files. To work around this issue users will need to change the parameter "core_pattern" in the /proc/sys/kernel/core_pattern file. The following command enables core files: sysctl -w kernel.core_pattern=core. The original setting is: /corefiles/core. In this state, the system looks for a directory named /corefiles, which does not exist, therefore a core file could not be created. | Linux |
| 125639 | There might be an issue when replicating VARRAYs with FLOAT(n) type to a target machine running Oracle 10g, due to the way that Oracle handles Float(n) types. Float is not an Oracle type; it is a SQL-92 type and Oracle is not consistent in the way that it handles the float type. This is a known Oracle bug. See Oracle bug report 4266304. | Oracle |
| 44626 | Users wishing to employ IOTs with overflow need to be running Oracle 11g or higher. This is a known Oracle issue addressed under 4627859. | Oracle |
| 53701 | There is a known issue with INSERT DIRECT LOAD VALUES (IDLV) in Oracle 11g that prevents the reading or modification of an object after modifying it in parallel. Oracle has provided three solutions for addressing this issue. They can be found in the Oracle update of SR6849411.993 dated 05-07-2008. This issue was fixed by Oracle in 11gR2. | Oracle |
| 59258 | Oracle versions 10.2.0.1 through 11.1.0.6 on AIX 5.3 (64 bit), members of SharePlex Admin group, other than the installation user, cannot run ora_setup or start SharePlex. Please see Oracle Bug # 6800649 and apply Patch 6800649. | Oracle |
| 75179 | Oracle 11gR2 - During a SYNC job, the copy of a new table (without data) failed at “EXP-00011: table does not exist” . The table that failed is a new table without any data. The EXP-00011 is caused by 11gR2 new feature "Deferred Segment Creation" that is controlled by the initialization parameter DEFERRED_SEGMENT_CREATION. The default is ON. To avoid this error, disable the parameter. A tar has been opened with Oracle and Oracle created a note 960216.1 Original Export Raises EXP-11 Table Does Not Exist. | Oracle |
| 92152 | OLTP compression with supplemental logging enabled may corrupt the Oracle Undo block, so Oracle suggests disabling supplemental logging when running OLTP compression. However, SharePlex requires supplemental logging to be enabled, so you may encounter this bug. This affects Oracle versions 11.2.0.2, 11.2.0.1 and 11.1.0.7. See Metalink ID 1191474.1. | Oracle |
To use the license utilities, such as to view, add, or remove license keys, see the SharePlex License Utilities section in the SharePlex Reference guide or SharePlex Installation and Setup Guide. For more information, contact your account manager.
SharePlex 11 requires new license keys.
License keys issued for versions prior to 11.0 will be incompatible with SharePlex 11.x. Existing customers should obtain a new license key before installing and/or upgrading to SharePlex 11.x. To obtain a new license key, please refer to the Licensing Assistance page on the Support Portal.
SharePlex 11.0 and above are available for installation on Linux and Unix platforms.
An 11.x version of SharePlex that can be natively installed on Windows will be delivered in the future. Customers who wish to replicate to and from sources and targets that run on Windows can either use the 10.x version of SharePlex or use remote replication, where the SharePlex software runs on a Linux server. Please see the System Requirements sections for details on supported source/target combinations with remote replication.
Note: To upgrade from SharePlex 10.x to 11.0 or 11.1, a new SharePlex license key must be requested. However, to upgrade from SharePlex 11.0 to 11.1, the existing effective SharePlex license key can be utilized.
Understanding SharePlex licensing and platform requirements
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.
Installing a trial version
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. For additional information, see the Install SharePlex section in the SharePlex Installation Guide.
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center
