Chatee ahora con Soporte
Chat con el soporte

SharePlex 12.0 - Release Notes

System Requirements and Conditions of Support When Replicating from Oracle

This chapter contains the requirements when capturing from an Oracle database and replicating to supported target databases.

Pre-requisite: At least the minimum level of supplemental logging must be enabled. Some SharePlex features may require PK/UK supplemental logging to be enabled.

Oracle source basics

This section contains the requirements for an Oracle database as a source when capturing from an Oracle database and replicating to supported target databases.

Supported operating systems

The following operating systems are supported for capture from a supported Oracle database and replication to an Oracle target database. For a list of supported source and target databases for Oracle capture, see Supported Source and Target Combinations.

SharePlex supports only the 64-bit version of the listed operating systems.

Supported operating systems via local installation:

Note:  SharePlex supports the following operating systems and only where the version matches the Oracle certified platforms. For example, Oracle 19c supports Linux 7 and later, therefore installation of SharePlex on a system with Oracle 19c is supported only on Linux 7 and later.

  • AIX 7.3

  • CentOS Linux 7.x

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x, 8.x, and 9.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

  • Ubuntu 22.04

  • Windows Server 2019 and 2022*

Limitations: For limitations related to Windows platform support, see the Windows-related issues in the Known Issues section.

* Unsupported features on the Windows platform:

  • PostgreSQL database as a source

  • Compare/Repair commands for Oracle to PostgreSQL replication

  • AVRO file format

  • MariaDB

  • sp_client utility

Supported versions

SharePlex supports the Standard and Enterprise Editions of Oracle 12cR1, 12cR2, 18c, 19c, 21c, and 23ai*.

Notes:
  • Unless specified, Oracle, RAC, and ASM are supported for the same versions.
  • SharePlex supports only the 64-bit version of Oracle Database
  • In addition to the supported operating systems for Oracle and the supported cloud platforms for Oracle, the Oracle versions listed above are also supported when running on an on-premises Oracle Exadata Database Machine. Any issues reported on an on-premises Oracle Exadata Database Machine will be tested against Oracle Exadata Cloud Service for reproduction purposes.

  • Amazon RDS for Oracle 12cR1 (supported 12cR1 versions are 12.1.0.2.v7 or later) and 19c. Support for Oracle features on Amazon RDS is limited to the default option groups: default:oracle-ee-12-1, default:oracle-ee-19, and default:oracle-se2-19.
  • On Windows Server, Oracle 19c versions below 19.6 have an Oracle bug (29865658) that causes the SharePlex ora_setup, Reader, and Poster processes to get stuck. This bug is fixed in version 19.6 and later.To avoid this issue with SharePlex, either upgrade the Oracle 19c database to version 19.6 or higher. Users need to contact Oracle to obtain a patch for bug 29865658 or set the CLIENT_STATISTICS_LEVEL database parameter to 'OFF'.

Steps to update the CLIENT_STATISTICS_LEVEL Database Parameter

  1. To see the current value of CLIENT_STATISTICS_LEVEL, use the following command:

    SQL> SHOW PARAMETER CLIENT_STATISTICS_LEVEL;

  2. If the current value is set to TYPICAL, update it to OFF using the following command:

    SQL> ALTER SYSTEM SET CLIENT_STATISTICS_LEVEL = 'OFF' SCOPE=SPFILE;

  3. To apply the change, restart the database by executing the following commands:

    SQL> SHUTDOWN IMMEDIATE;

    SQL> STARTUP;

*Conditions of Support for Oracle 23ai:

  • Oracle 23ai is supported on DBCS, ExaCS/CC, and Oracle On-premises Exadata platforms.

  • On Oracle 23ai, the Copy/Append command is not supported with encrypted tablespaces.

  • In 23ai, when creating a table with an XMLType column, it is created with a default storage type of TRANSPORTABLE BINARY XML. To enable SharePlex support, change the XMLType column’s storage type to BINARY XML.

Supported cloud platforms

Oracle Cloud Infrastructure:

  • Oracle Exadata Cloud Service (ExaCS)1
  • Oracle Exadata Cloud@Customer (ExaCC)1
  • Oracle Database Cloud Service (DBCS)2
    • Enterprise Standard Edition

    • Enterprise Edition High Performance

    • Enterprise Edition Extreme Performance

  • Oracle Compute (IaaS) Virtual Machines and Bare Metal

Amazon Web Services:

  • Amazon RDS for Oracle 3
  • Amazon EC2 (IaaS) Virtual Machine

Microsoft Azure:

Azure Virtual Machine (IaaS)

Conditions of support
  1. Oracle Exadata: Issues on Oracle Exadata will be tested against Oracle Exadata Cloud Service for reproduction purposes.

  2. Oracle Database Cloud Service (DBCS): SharePlex only supports Transparent Data Encryption (TDE) feature on DBCS EE-HP, DBCS EE-EP, and ExaCS/CC.

  3. Amazon RDS for Oracle: Please see Supported Oracle Source and Target Versions for additional clarification on version compatibility.

Oracle source basic conditions of support

Non-supported Oracle features

This is a list of commonly used Oracle features which SharePlex does not replicate and are not listed elsewhere in this document. Since both Oracle and SharePlex continually change and improve, this list of exclusions cannot be considered complete. Unless an item is stated here as being supported, assume that SharePlex does not replicate it.

Object/operation/feature Not supported
Oracle operations Operations that do not appear in the redo logs. This includes any DML or DDL not in the redo logs, and also PL/SQL packages which do not write results to the redo logs, for example, dbms_shared_pool.keep and related packages.

dbms_scheduler.create_job

This object is not supported.

Flashback

SharePlex does not support the Oracle Flashback Table feature. If the SP_REPLICATE_ALL_DDL parameter is enabled (value of 1), SharePlex may try to replicate the flashback DDL, which will return an error. To perform Flashback Table on a table that is in replication, use the following procedures in the SharePlex Administrator Guide to work around this issue:

  1. Remove source objects from replication
  2. Perform the flashback
  3. Add or change objects in an active configuration
Special characters
  • SharePlex currently does not support the use of a dot (.) in Oracle schema names or in Oracle objects such as , sequences, tables, columns, materialized views, synonyms, users, and other related objects.

  • If a quoted username (Oracle allows quoted identifier names) is used during Ora_setup, the setup process will fail, and subsequent configuration activation will also fail.

Additional information about data types

Notes about open target data type support 

  • Replication of SecureFile LOBS to non-Oracle databases is supported except if the storage specification includes any level of compression, encryption, and/or deduplication.
  • Replication of LOB operations generated by dbms_lob are not supported when replicating to non-Oracle targets.

  • SharePlex applies replicated Oracle data to the target according to the data type of the target column, rather than mapping to a default data type. Corresponding source and target columns must contain compatible data types to ensure successful DML operations.
  • If the precision or size of the target data type is not large enough for the data being replicated, the target database may truncate or round the data when SharePlex applies it.

SharePlex does not support the replication of data from Oracle to open targets for the below Extended Data Types: 

  • VARCHAR2 (4000-32767)
  • NVARCHAR2 (4000-16383)
  • RAW (2000-32767)
Supported / non-supported SharePlex features for Oracle to open targets replication

The following table shows whether specific SharePlex features are supported for replication from Oracle to open targets.

SharePlex feature Supported open targets
reconcile command (target instantiation) All
Compare/Compare Using and repair/repair using commands* PostgreSQL
copy/copy using and append/append using commands Not supported
Hash horizontally partitioned replication All
Column-based horizontally partitioned replication All
Vertically partitioned replication All
Column mapping All
Key definition All
Build configuration with scripts Not supported
Named queues All
Commit Reduction (feature of Post Enhanced Performance) All
Dependency Checking (feature of Post Enhanced Performance) Not supported
Transformation Not supported
Conflict resolution

PostgreSQL

Peer-to-peer replication (bi-directional) PostgreSQL
Consolidated replication (many to one) All
Broadcast replication (one to many) All
High availability replication (active/passive bi-directional) PostgreSQL
Change tracking target (CDC) Not supported
Data encryption All
Data compression All
SSH All
auth_hosts file All
Monitoring scripts All
SNMP monitoring All
Continue posting on error (SP_OPX_CONT_ON_ERR) All
Suspend on out of sync errors (SP_OPX_OUT_OF_SYNC_SUSPEND) All
Reduced key (SP_OPX_REDUCED_KEY) All
Logical Transaction Rollback on out-of-sync transactions Not supported
HSM: Oracle database wallet key store on external storage using sp_hsm utility All

* The Compare and Repair commands for Oracle to PostgreSQL replication are certified for use with Oracle 18c, 19c, and 21c.

System requirements for replication of OLTP compressed data

This chapter contains the requirements when capturing OLTP compressed data from an Oracle source database and replicating it to a supported target database.

Supported operating systems

The following operating systems are supported for capture from a supported Oracle database and replication to a supported target database.

SharePlex supports only the 64-bit version of the listed operating systems.

For OLTP, SharePlex supports the following operating systems only:

  • AIX 7.3
  • CentOS Linux 7.x
  • HP-UX 11.31 Itanium
  • Oracle Linux 7.x, 8.x, and 9.x
  • Oracle Solaris SPARC 11.4
  • RHEL 7.x, 8.x, and 9.x
  • Rocky Linux 8.x
  • SuSE SLES 12.x and 15.x

  • Windows Server 2019 and 2022

Supported Oracle database version/s

SharePlex supports the Standard and Enterprise Editions of Oracle 12cR1, 12cR2, 18c, 19c, and 21c for replicating the OLTP compressed data.

Supported objects and operations for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to an Oracle or an open target.

Note: Replication to targets with a different character set is supported, with limitations. When posting to open target databases, XML files and JMS, SharePlex supports only UNICODE and US7ASCII on the target, but conversion can be performed by an Oracle client installed on the target system. For full details, see the Preinstallation Checklist in the SharePlex Installation and Setup Guide.

Tables

SharePlex supports the following DML operations on tables:

  • INSERT, UPDATE, DELETE, COMMIT, ROLLBACK
  • Direct-path loads (SQL*Loader) (INSERT AND FULL ROLLBACK).

Note: Replication of partial rollbacks of DLOADs is not supported.

The target table must support the column types that are being replicated from the source Oracle table.

SharePlex supports the following table types for DML operations:

Supported table type*

Conditions of Support

Regular Oracle tables

None

Index-organized tables

SharePlex does not support:

  • Replication to/from index-organized tables that contain LOB or VARRAY columns
  • Replication from a non-index-organized table to an index-organized table
  • SharePlex hash-based horizontal partitioning of index-organized tables

Partitioned tables

None

Views

None

Materialized views

SharePlex does not support replication from a materialized view to a materialized view. SharePlex can replicate the underlying table of a materialized view to a regular target table.

SharePlex does not support the following table types:

  • Replication to/from nested tables
  • Replication to/from clustered tables

*SharePlex does not support the following for any table type:

  • Replication to/from Identity columns.
  • Replication of rows changed by 'UPDATE WITH CASE' syntax.
  • Replication of rows in which data exceeds 319 KB in size, excluding LOB and LONG columns
  • Replication of external tables or tables with external partitions

Sequences
  • Transactional changes to Oracle sequences can be replicated only from Oracle to Oracle.
  • To replicate transactional changes to sequences, the supplemental logging of primary and unique keys must be enabled at the database level, or you must enable supplemental logging for primary keys on the sys.seq$ table.
Secured and compressed objects

SharePlex supports DML operations on secured or compressed objects as described in the following table. See "Conditions of support" following this table for additional information.

Secured/Compressed Object Can be replicated to:
DML on tables encrypted by Oracle Obfuscation Toolkit All target types

DML on tables with Transparent Data Encryption (TDE)1

All target types

DML on Oracle Label Security (OLS)2

All target types

DML on compressed objects: Basic, Advanced Row (OLTP) Compression, HCC3

All target types

Direct Load (DLOAD) on compressed objects: Basic, Advanced Row (OLTP) Compression, HCC3

All target types
Conditions of support

1. TDE

  • SharePlex supports Tablespace Encryption and Column Encryption, both source and target.

  • The SharePlex  copy/append command does not support TDE.

  • TDE is not supported for sources on RDS.

  • SharePlex only supports the AES and DES encryption algorithms.

2. OLS

By default, SharePlex cannot process rows that are protected by OLS (Oracle Label Security) because users granted DBA privileges (like SharePlex) do not have enough privileges to access those rows. However, if privilege is granted from the OLSSYS user, SharePlex can support OLS. SharePlex was tested under the following OLS configuration:

  • The SharePlex user was granted full privilege to the objects in replication.
  • Test tables with OLS security were created.
  • Data was replicated using INSERT, UPDATE, DELETE, ROLLBACK, and TRUNCATE operations, and ALTER TABLE to add and drop columns.

Note: If the OLS policy data label column is defined as hidden, the data in that column cannot be replicated by SharePlex.

Important: Shareplex does not support OLS policy configuration changes on tables during active replication. Users need to apply these configurations before activating the configuration.

3. Compression

For HCC compression: SharePlex does not support query low compression. Supported types of compression are query high, archive low and archive high.

For Advanced Row (OLTP) Compression: Under certain conditions, Oracle does not provide enough information in the redo log for SharePlex to replicate a DML operation on a OLTP compressed object. Testing of OLTP compressed objects is advised.

Oracle to open targets DDL support

SharePlex provides default and optional DDL support.

Notes: ALTER TABLE to ADD COLUMN and ALTER TABLE to DROP COLUMN are supported on Basic, Advanced Row (OLTP) Compression, and HCC compressed Oracle objects for replication to all Oracle and open targets.

SharePlex does not support:

  • ANALYZE TABLE and ANALYZE INDEX
  • DDL to ALTER TABLE ADD OVERFLOW to an IOT in replication
  • DDL operations issued by the SharePlex database user
  • DDL to ALTER INDEX to an IOT in replication

SharePlex provides limited DDL support for replication from Oracle to open targets. The involved objects must be listed in the active configuration file explicitly or with a wildcard. There is no optional DDL support for replication from Oracle to cross platforms.

The default Oracle to open target configuration is represented by the following parameter setting:

SP_OCT_REPLICATE_DDL=3

See "Table Notes" following this table for additional information.

Supported object Supported Operation
Table and IOT Truncate1
Alter table add column2
Alter table drop column
Table Notes:
  • TRUNCATE TABLE is not supported from Oracle compressed objects to open targets.

  • The default mappings of Oracle data types to their open target counterpart for replicated ALTER TABLE ADD COLUMN DDL are shown in the "Supported Data type" section of the respective target. When adds the column, it defines it with the default data type. This mapping applies to the entire configuration (not per table).

Oracle to Azure Event Hubs replication

SharePlex supports replication from Oracle to Azure Event Hubs, according to the details below.

Supported target operating systems

SharePlex replicates remotely to the Azure Event Hubs service. Remote replication from the following operating systems is supported:

  • CentOS Linux 7.x

  • Oracle Linux 7.x, 8.x, and 9.x

  • RHEL 7.x, 8.x, and 9.x

  • SuSE SLES 12.x and 15.x

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Supported Azure Event Hubs target

Supported platform as a service: Azure Event Hubs

Supported file types

Supported operations and objects for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to an Azure Event Hubs target. For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL replication

SharePlex supports DDL operations on tables and sequences, with some conditions. DDL can be replicated from an Oracle source to an Azure Event Hubs target. For additional information, see Oracle to open target DDL support.

Oracle to File Output replication

SharePlex supports replication from Oracle to File Output, according to the details below.

Supported target operating systems

Supported operating systems via local installation:

  • AIX 7.3

  • CentOS Linux 7.x

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x, 8.x, and 9.x

  • Oracle Solaris SPARC 11.4

  • Oracle Solaris x86 11.4

  • RHEL 7.x, 8.x, and 9.x

  • SuSE SLES 12.x and 15.x

  • Rocky Linux 8.x

  • Windows Server 2019 and 2022

NOTE: SharePlex supports only the 64-bit version of the listed operating systems.

Supported file types

  • XML file
  • SQL file
  • JSON file
XML format supported open targets

This mapping applies to all targets that receive messages as XML:

  • File in XML format
  • JMS
  • Kafka
  • Azure/Kafka Event Hubs
Oracle XML
BINARY_DOUBLE decimal
BINARY_FLOAT decimal
BLOB base64Binary
CHAR string
CLOB string
DATE dateTime
INTERVAL DAY TO SECOND dayTimeDuration
INTERVAL YEAR TO MONTH yearMonthDuration
LONG string
NCHAR string
NCLOB string
NUMBER decimal
NVARCHAR2 string
RAW base64Binary
ROWID string
TIMESTAMP dateTime
TIMESTAMP WITH LOCAL TIME ZONE dateTimeStamp
TIMESTAMP WITH TIME ZONE dateTimeStamp
VARCHAR2 string
VARRAY Post maps the data types in the source VARRAY to the appropriate XML data types. Only certain data types in a VARRAY are supported. See the conditions of support.
Conditions of support

Only the following data types in a VARRAY are supported by SharePlex when replicating to XML output:

  • BINARY_FLOAT
  • VARCHAR2
  • BINARY_DOUBLE
  • NUMBER
  • TIMESTAMP (This is converted to a DATE data type without microseconds in XML output)
  • DATE
  • UDT (only if it contains one of the data types in this list)

See Conditions of support for the above-mentioned supported data types.

JSON format supported open targets

This mapping applies to all targets that receive messages as JSON:

  • File in XML format
  • JMS
  • Kafka
  • Azure/Kafka Event Hubs
Oracle JSON
BINARY_DOUBLE Number
BINARY_FLOAT Number
BLOB String containing base64 encoded data
CHAR String
CLOB String
DATE String containing date
INTERVAL DAY TO SECOND String containing interval
INTERVAL YEAR TO MONTH String containing interval
LONG String
NCHAR String
NCLOB String
NUMBER Number
NVARCHAR2 String
RAW String containing hex encoded data
ROWID String
TIMESTAMP String containing timestamp
TIMESTAMP WITH LOCAL TIME ZONE String containing timestamp
TIMESTAMP WITH TIME ZONE String containing timestamp
VARCHAR2 String

Conditions of support: See Conditions of support for the above-mentioned supported data types.

Supported operations and objects for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to a File Output target. For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL replication

SharePlex supports DDL operations on tables and sequences, with some conditions. DDL can be replicated from an Oracle source to a File Output target. For additional information, see Oracle to open target DDL support.

Oracle to JMS Message Queues replication

SharePlex supports replication from Oracle to JMS Message Queues, according to the details below.

Supported target operating systems

Local SharePlex installation is supported on the below operating systems:

  • AIX 7.3

  • CentOS Linux 7.x

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x, 8.x, and 9.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 2019 and 2022

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Supported JMS Message Queues

  • JMS - Apache ActiveMQ 5.8 and 5.16.7
  • JMS - IBM MQ 8 and 9.3

Supported file types

Supported operations and objects for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to a JMS Message Queues target. For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL replication

SharePlex supports DDL operations on tables and sequences, with some conditions. DDL can be replicated from an Oracle source to a JMS Message Queue target. For additional information, see Oracle to open target DDL support.

Oracle to Kafka replication

SharePlex supports replication from Oracle to Kafka, according to the details below.

Supported target operating systems

Supported operating systems via local installation:

  • CentOS Linux 7.x

  • Oracle Linux 7.x, 8.x, and 9.x

  • RHEL 7.x, 8.x, and 9.x

  • SuSE SLES 12.x and 15.x

  • Rocky Linux 8.x

Remote replication from the following operating systems is supported:

  • CentOS Linux 7.x

  • Oracle Linux 7.x, 8.x, and 9.x

  • RHEL 7.x, 8.x, and 9.x

  • SuSE SLES 12.x and 15.x

  • Rocky Linux 8.x

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Supported Kafka targets

  • Apache Kafka 3.6.1 and 3.8

  • Confluent Kafka 7.6.0

Confluent Kafka, along with Schema Registry and AVRO format, supports the following authentication methods:

  • SASL_PLAINTEXT with PLAIN authentication

  • Kerberos SASL_PLAINTEXT with GSSAPI authentication

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.

Supported formats

AVRO format supported data types

Note: SharePlex supports the AVRO format with Confluent Kafka version 7.6.0 and the JDBC connector version confluentinc-kafka-connect-jdbc-10.7.6.

Oracle Kafka ( AVRO format)
VARCHAR2 string
CHAR string
ROWID string
NUMBER (P, S <= 0)

P-S < 10 -> int

P-S < 19 -> long

P-S >= 19 -> decimal (logical)

NUMBER (P, S > 0) decimal (logical)
BINARY FLOAT float
BINARY DOUBLE double
DATE date (logical)/string
TIMESTAMP timestamp-millis (logical)/string
TIMESTAMP_TZ timestamp-millis (logical)/string
TIMESTAMP_LTZ timestamp-millis (logical)/string
INTERVAL_YEAR string
INTERVAL_DAY string
RAW bytes
CLOB string
BLOB bytes
LONG string
LONG VARCHAR string
LONG RAW bytes
Limitations:
  • An UPDATE on a key column results in a DELETE operation followed by the INSERT. If the UPDATE does not include data for LOB columns, those columns will become empty.

  • The Confluent kafka-connect-jmespath predicate plugin, used for filtering fields, does not support the AVRO BYTES datatype. Therefore, binary LONGs/LOBs (such as LONG RAW and BLOB) mapped to AVRO BYTES cannot be filtered out. When such columns lack data, they are populated with the value _splex_default during updates, which must be filtered out using appropriate transform and predicate configurations.

  • Commit operations are not directly posted as commits. They are handled by the JDBC Sink Connector and are configurable with JDBC Sink Connector configurations, which commits after a configurable limit is reached.

  • TRUNCATE operations are not supported by the JDBC Sink Connector. The Poster will ignore any TRUNCATE transactions.

  • DateTime Handling with AVRO parameter datetime_logical set to yes using the Target command datetime_logical = yes:

    • Timestamp precision is supported up to milliseconds.

    • Timestamps with timezones do not retain timezone information and must be mapped to TIMESTAMP.

    • DATE and TIMESTAMP can store values only after 01-Jan-1970. If earlier values are received, processing stops with an error.

  • If an Oracle Date datatype includes TIME, the JDBC Sink Connector will fail to insert the record in the Oracle target database when datetime_logical is set to `no` and the date format includes time.

Supported operations and objects for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to a Kafka target. For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL replication

SharePlex supports DDL operations on tables and sequences, with some conditions. DDL can be replicated from an Oracle source to a Kafka target. For additional information, see Oracle to open target DDL support.

Oracle to MariaDB replication

SharePlex supports replication from Oracle to MariaDB, according to the details below.

Supported target operating systems

Supported operating systems via local 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 and 8.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x and 8.x

Supported target operating systems via remote replication:

  • AIX 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

  • Rocky Linux 8.x

  • SuSE SLES 12.x and 15.x

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Limitation: The SP_OPX_THREADS parameter is not supported in MariaDB.

Supported target versions and ODBC requirements

MariaDB 11.4.2

ODBC driver requirement:

mariadb-connector-odbc-3.1.20-1.x86_64

Supported target cloud platforms

Amazon Web Services: Amazon RDS for MariaDB

Supported data types

SharePlex supports the following data types for replication from Oracle to MariaDB:

Oracle MariaDB
BINARY_DOUBLE 1 DOUBLE
BINARY_FLOAT DOUBLE
BLOB LONGBLOB
CHAR (n) CHAR (n)
CLOB LONGTEXT
DATE DATETIME (0)
LONG LONGTEXT
LONGRAW LONGBLOB
NUMBER DOUBLE
NUMBER (p,0:) NUMERIC (p,s)
NUMBER (p,s) DOUBLE
RAW (n) VARBINARY (n)
TIMESTAMP (7:9) DATETIME (6)
TIMESTAMP (p) DATETIME (p)
VARCHAR2 (n) VARCHAR (n)
Conditions of support: Because Oracle and MariaDB handle this data type differently, there may be a very small difference in precision between the value of the source and the value of the target row. You may see the difference when viewing the data from SQL*Plus or other utility, but SharePlex will not report this difference as an out-of-sync condition.

Supported operations and objects for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to a MariaDB target. For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL replication

SharePlex supports DDL operations on tables and sequences, with some conditions. DDL can be replicated from an Oracle source to a MariaDB target. For additional information, see Oracle to open target DDL support.

Oracle to MySQL replication

SharePlex supports replication from Oracle to MySQL, according to the details below.

Supported target operating systems

Supported operating systems via local installation:

  • RHEL 7.x and 8.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x and 8.x

  • Windows Server 2019 and 2022

Remote replication from the following operating systems is supported:

  • RHEL 7.x and 8.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x and 8.x

  • Windows Server 2019 and 2022

Supported target operating systems via remote replication:

  • AIX 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

  • Rocky Linux 8.x

  • SuSE SLES 12.x and 15.x

  • Windows Server 2019 and 2022

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Limitation: The SP_OPX_THREADS parameter is not supported in MySQL.

Supported target versions and ODBC requirements

MySQL 8.0.26

ODBC driver requirement:

ODBC 8.0.26 for Linux

Supported target cloud platforms

Amazon Web Services

  • Amazon RDS for MySQL
  • Amazon Aurora

Microsoft Azure

  • Azure Virtual Machine (IaaS)
  • MySQL Azure database (PaaS)

Supported data types

SharePlex supports the following data types for replication from Oracle to MySQL:

Oracle MySQL
BINARY_DOUBLE 1 DOUBLE
BINARY_FLOAT DOUBLE
BLOB LONGBLOB
CHAR (n) CHAR (n)
CLOB LONGTEXT
DATE DATETIME (0)
LONG LONGTEXT
LONGRAW LONGBLOB
NUMBER DOUBLE
NUMBER (p,0:) NUMERIC (p,s)
NUMBER (p,s) DOUBLE
RAW (n) VARBINARY (n)
TIMESTAMP (7:9) DATETIME (6)
TIMESTAMP (p) DATETIME (p)
VARCHAR2 (n) VARCHAR (n)
Conditions of support
  1. Because Oracle and MySQL handle this data type differently, there may be a very small difference in precision between the value of the source and the value of the target row. You may see the difference when viewing the data from SQL*Plus or other utility, but SharePlex will not report this difference as an out-of-sync condition.

See Conditions of support for the above-mentioned supported data types.

Supported operations and objects for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to a MySQL target. For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL replication

SharePlex supports DDL operations on tables and sequences, with some conditions. DDL can be replicated from an Oracle source to a MySQL target. For additional information, see Oracle to open target DDL support.

Oracle to Oracle replication

SharePlex supports replication from Oracle to Oracle, according to the details below.

Supported target operating systems

Supported operating systems via local installation:

  • AIX 7.3

  • CentOS Linux 7.x

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x, 8.x, and 9.x

  • Oracle Solaris SPARC 11.4

  • Oracle Solaris x86 11.4

  • RHEL 7.x, 8.x, and 9.x

  • SuSE SLES 12.x and 15.x

  • Rocky Linux 8.x

  • Ubuntu 22.04

  • Windows Server 2019 and 2022

Remote replication from the following operating systems is supported:

Note: By using remote replication, database running on Solaris SPARC 11.1, 11.2, and 11.3 or Windows 2012, 2012 r2, and 2016 can leverage remote replication to capture and/or post data using SharePlex installed on Solaris SPARC 11.4, or Windows 2019 and 2022 respectively ensuring replication continues without the need for direct installation on the unsupported platform.

  • AIX 7.3

  • CentOS Linux 7.x

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x, 8.x, and 9.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

  • Ubuntu 22.04

  • Windows Server 2019 and 2022

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Supported target versions

SharePlex supports the Standard and Enterprise Editions of Oracle 12cR1, 12cR2, 18c, 19c, 21c, and 23ai*.

Notes:
  • Unless specified, Oracle, RAC, and ASM are supported for the same versions.
  • SharePlex supports only the 64-bit version of Oracle Database
  • In addition to the supported operating systems for Oracle and the supported cloud platforms for Oracle, the Oracle versions listed above are also supported when running on an on-premises Oracle Exadata Database Machine. Any issues reported on an on-premises Oracle Exadata Database Machine will be tested against Oracle Exadata Cloud Service for reproduction purposes.
  • Amazon RDS for Oracle 12cR1 (supported 12cR1 versions are 12.1.0.2.v7 or later) and 19c. Support for Oracle features on Amazon RDS is limited to the default option groups: default:oracle-ee-12-1, default:oracle-ee-19, and default:oracle-se2-19.
  • On Windows Server, Oracle 19c versions below 19.6 have an Oracle bug (29865658) that causes the SharePlex ora_setup, Reader, and Poster processes to get stuck. This bug is fixed in version 19.6 and later.To avoid this issue with SharePlex, either upgrade the Oracle 19c database to version 19.6 or higher. Users need to contact Oracle to obtain a patch for bug 29865658 or set the CLIENT_STATISTICS_LEVEL database parameter to 'OFF'.

*Conditions of Support for Oracle 23ai:

  • Oracle 23ai is supported on DBCS, ExaCS/CC, and Oracle On-premises Exadata platforms.

  • On Oracle 23ai, the Copy/Append command is not supported with encrypted tablespaces.

Supported target cloud platforms

Oracle Cloud Infrastructure

  • Oracle Exadata Cloud Service (ExaCS)1
  • Oracle Exadata Cloud@Customer (ExaCC)1
  • Oracle Database Cloud Service (DBCS)2
    • Enterprise Standard Edition

    • Enterprise Edition High Performance

    • Enterprise Edition Extreme Performance

  • Oracle Compute (IaaS) Virtual Machines and Bare Metal

Amazon Web Services

  • Amazon RDS for Oracle 3
  • Amazon EC2 (IaaS) Virtual Machine

Microsoft Azure

Azure Virtual Machine (IaaS)

Conditions of support
  1. Oracle Exadata: Issues on Oracle Exadata will be tested against Oracle Exadata Cloud Service for reproduction purposes.

  2. Oracle Database Cloud Service (DBCS): SharePlex only supports Transparent Data Encryption (TDE) feature on DBCS EE-HP, DBCS EE-EP, and ExaCS/CC.

  3. Amazon RDS for Oracle: Please see Supported Oracle Source and Target Versions for additional clarification on version compatibility.

Supported data types

SharePlex supports the following Oracle data types for replication to Oracle targets. See the Conditions of support for additional information.

  • ANYDATA 1
  • B-FILE
  • BINARY DOUBLE 7
  • BINARY FLOAT 7
  • BLOB 2
  • CHAR
  • CLOB 2
  • DATE
  • INTERVAL
  • LONG RAW2
  • LONG 2
  • NCHAR
  • NCLOB 3
  • NUMBER
  • NVARCHAR2 8
  • RAW 8
  • ROWID
  • SDO_GEOMETRY
  • TIMESTAMP
  • TIMESTAMP WITH LOCAL TIME ZONE
  • TIMESTAMP WITH TIME ZONE
  • UDT (User Defined Type)5
  • UROWID
  • VARCHAR
  • VARCHAR2 8
  • VARRAY collectors
  • XMLTYPE 4

Note: SharePlex supports columns that are defined as INVISIBLE.

Conditions of support

1. ANYDATA

  • Replication of ANYDATA is supported, except when it contains a UDT or the storage is defined as SecureFile LOB with compression. SecureFile LOB without compression is supported. Only the following data types within ANYDATA are supported by SharePlex:

    • CHAR
    • DATE
    • NUMBER
    • RAW
    • VARCHAR
    • VARCHAR2
    • TIMESTAMP
  • A data type within an ANYDATA type must be in-row (inside the column data). Oracle encapsulates the ANYDATA type as an in-row secure file LOB. If the encapsulated data is longer than the length allowed for an in-row LOB, that data appears as out-of-row LOB data. SharePlex assumes that the encapsulated data always appears as in-row LOB.

2. LONG and LOB (BLOB, CLOB)

  • Any table that contains a LOB or LONG should have a primary key or unique key defined on it. If a table does not have a key, SharePlex builds its own key from all of the columns except LONGs or LOBs. If a LOB or LONG is the only difference between two rows that otherwise satisfy the Post WHERE clause, SharePlex cannot guarantee that the correct row will be updated.
  • SharePlex supports SecureFiles LOBs as follows:

    • Logging must be enabled.
    • SharePlex supports uncompressed SecureFiles LOBS and SecureFiles LOBS with high or medium compression (compressed with ZLIB or ZSTD compression libraries)
    • SecureFiles LOBS are not supported when the storage specification includes encryption and/or deduplication.
  • SharePlex does not support LONG and LONG_RAW data types in a configuration where transformation or conflict resolution are performed.

3. NCLOB

NCLOBs are not supported by Compare/Repair if the source and target have different character sets.

4. XMLTYPE

SharePlex supports the replication of XMLTYPE stored as CLOB and BINARY. SharePlex does not support XMLTYPE stored as OBJECT RELATIONAL or TRANSPORTABLE BINARY. Additionally, the following applies:

  • XMLTYPE stored as BINARY is not supported when the storage is defined as SecureFile LOB with compression. SecureFile LOB without compression is supported.

  • Binary XMLTypes are not supported by Compare/Repair when the source and target character sets are different and require character set conversion.
  • Compare/Repair does not support comparison of XMLTYPE when the source and target have different storage clauses. Compare/Repair only supports compare/repair when source and target are both stored as BINARY or both are stored as CLOB.

5. User-defined types

SharePlex does not support abstract data types and VARRAYs in a configuration where the SharePlex conflict resolution feature is performed.

NOTE: SharePlex replicates tables with the UDT fields in the base type ONLY. In case of columns containing multiple subtypes, replication is applicable only for base type fields.

6. General

If the precision or size of the target data type is not large enough for the data being replicated, the data may be truncated or rounded by the database when applied.

7. BINARY DOUBLE and BINARY FLOAT

The BINARY DOUBLE and the BINARY FLOAT data types are not supported for the copy command.

8. Extended Data Types

  • Extended Data Types are not supported for the copy command.
  • Extended Data Types are not supported on a key column. The keys that do not support the Extended Data Types include:
    • Primary key on the Oracle table
    • Unique key on the Oracle table
  • Horizontal partitioning is not supported by tables containing the Extended Data Type columns.
  • SharePlex does not replicate data with Extended Data Type when target type is JMS Message Queues, File output (XML, JSON, SQL), Event Hubs, or Kafka.

Supported operations and objects for DDL replication

SharePlex provides default and optional DDL support.

Note: ALTER TABLE to ADD COLUMN and ALTER TABLE to DROP COLUMN are supported on Basic, Advanced Row (OLTP) Compression, and HCC compressed Oracle objects for replication to all Oracle and open targets.

SharePlex does not support:

  • ANALYZE TABLE and ANALYZE INDEX
  • DDL to ALTER TABLE ADD OVERFLOW to an IOT in replication
  • DDL operations issued by the SharePlex database user
  • DDL to ALTER INDEX to an IOT in replication
  • During DDL replication, data containing the ALTER statement related to Oracle extended statistics—'Virtual by User'— is not supported. Oracle also does not recommend to use the extended stastistics 'Virtual by User'.

DDL on objects listed in the active configuration file

SharePlex supplies default and optional DDL replication for objects whose names are listed in the configuration file explicitly or by wildcard. See "Conditions of support" following this table for additional information.

For details about the controlling parameter, see the SharePlex Reference Guide.

Supported object Supported DDL Operation

Enabled by default?

Controlling parameter

Table and IOT

(when they exist in the source at the time of configuration activation)

Truncate

Alter to add, drop, modify columns

Alter to add, modify, drop, split, coalesce, move, truncate, exchange partition or subpartition1

Drop Table

Yes

SP_OCT_REPLICATE_DDL=3

Table and IOT

(when they are added to the source after configuration activation)

Create

Create as Select2

Yes

SP_OCT_AUTOADD_ENABLE=1

Table Alter Table Rename Yes SP_OCT_DDL_UPDATE_CONFIG=1
Index

Create

Alter

Drop

Yes

SP_OCT_AUTOADD_ENABLE=1

Materialized View3

Create

Drop

No

SP_OCT_AUTOADD_ENABLE=1 and

SP_OCT_AUTOADD_MVIEW=1 and

SP_SYS_TARGET_COMPATIBILITY=8.6.2 or higher

Sequences4

Create, Drop

No

SP_OCT_AUTOADD_ENABLE=1 and

SP_OCT_AUTOADD_SEQ=1 and

SP_SYS_TARGET_COMPATIBILITY=8.6.3 or higher

Trigger

Create, Drop

No

SP_OCT_REPLICATE_TRIGGER=1

Synonym

Create, Drop

No

SP_OCT_REPLICATE_SYNONYM=1
Grant5 Create, Drop

No

SP_OCT_REPLICATE_GRANT=1
Conditions of support
  1. ALTER TABLE has the following conditions of support:
    • ALTER TABLE DDL that involves multiple tables, such as EXCHANGE PARTITION between tables, requires all tables involved to be in replication.
    • Default DDL support for ALTER TABLE on partitions/subpartitions applies to user-named interval partitions/subpartitions. For system-named (system generated) interval partitions/subpartitions, SharePlex supports only ALTER TABLE to DROP and TRUNCATE the system-named partitions. To enable support for DROP and TRUNCATE of system-named partitions, set the SP_OCT_TRUNC_PARTITION_BY_ID parameter to 1, and ensure that both source and target are updated to SharePlex version 8.6.4 or later. NOTE: This requirement has changed from previous SharePlex releases in that the parameter must now be set regardless of the Oracle version, including for Oracle 12.2 and later.
    • SharePlex does not support TRUNCATE of a system-generated sub-partition if the sub-partition is empty. In such cases, Post stops with error SP-OPO01002. To configure Post to ignore this error, stop Post, set the SP_OPO_CONT_ON_ERR parameter to 1, and add error number SP-OPO01002 to the top of the oramsglist file. See the SharePlex Reference Guide for more information about this parameter.
  1. For CREATE TABLE AS SELECT, SharePlex supports the following data types: LONG, DATE, RAW, LONG RAW, ROWID, LONG VARCHAR, CHAR, CLOB, BLOB, CFILE, BFILE, TIMESTAMP, INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND, VARCHAR2, NUMBER, and ANYDATA.
  2. For CREATE MATERIALIZED VIEW the following applies:

    • SharePlex supports the following data types for CREATE MATERIALIZED VIEW: LONG, DATE, RAW, LONG RAW, ROWID, UROWID, LONG VARCHAR, CHAR, CLOB, BLOB, CFILE, BFILE, TIMESTAMP, INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND, VARCHAR2, NUMBER, and ANYDATA. SharePlex does not support ALTER MATERIALIZE VIEW.
    • SharePlex converts a CREATE MATERIALIZED VIEW to a CREATE TABLE, applies the CREATE TABLE to the target, and then replicates the DML that populates the view. SharePlex does not replicate materialized views to materialized views.
  3. To replicate sequences, the supplemental logging of primary and unique keys must be enabled at the database level, or you must enable supplemental logging for primary keys on the sys.seq$ table.

  4. Amazon RDS restricts DBA users from issuing the GRANT command. Because SharePlex runs as the DBA user, SharePlex cannot replicate GRANT to or from an RDS database.

DDL on objects not listed in the active configuration file

SharePlex provides expanded DDL support for Oracle objects that are not listed in the configuration file. SharePlex replicates the DDL statements for these objects, but does not maintain synchronization of the objects through DML replication. Expanded DDL replication is optional and is enabled with the following parameter setting:

SP_OCT_REPLICATE_ALL_DDL=1

Note: Expanded DDL replication supports not only tables and sequences but also a wide range of other objects such as procedures, functions, users, and views, which are not part of replication. Some of these objects may have underlying objects that are in replication. In those cases, Expanded DDL replication applies to the underlying objects in replication, as well as to the object that is not in replication.

See "Table Notes" following this table for additional information.

Supported object Supported Operation
Table and IOT Create table
Create table as select
Alter table add column
Alter table drop column
Drop table
Truncate
Comment on table
Comment on columns
Associate Statistics
Disassociate Statistics
Cluster Create cluster
Crop cluster
Sequence Create
Drop
Alter

Partition/ Subpartition

Add
Split
Merge
Drop
Modify
Coalesce
Exchange
Move
Truncate
Rename
Set
Index Create
Alter
Drop
View Create
Alter
Drop
Comment on view
Synonym Create
Drop
Directory1 Create
Drop
User-defined type Create type
Alter type
Drop type
Create type body
Drop type body
Stored procedure Create
Alter
Drop
Stored function Create
Alter
Drop
Package Create package
Create package body
Alter package
Alter package body
Drop package
Drop package body
User Create user
Alter user
Drop user
Grant1
Revoke
Role Create role
Alter role
Drop role
Grant1
Revoke
Table Notes:

Amazon RDS restricts DBA users from issuing certain commands on an Amazon RDS database instance. Because SharePlex runs as the DBA user, SharePlex cannot replicate the following commands to or from an RDS database:

  • CREATE or DROP DIRECTORY
  • GRANT

Supported operations and objects for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to an Oracle target. For additional information, see Supported Operations and Objects for DML Replication.

Oracle to PostgreSQL replication

SharePlex supports replication from Oracle to PostgreSQL, according to the details below.

Supported target operating systems

Supported operating systems via local installation:

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x and 8.x

  • Ubuntu 22.04

  • Windows Server 2019 and 2022

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

  • Ubuntu 22.04

  • Windows Server 2019 and 2022

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Supported target versions and ODBC requirements

  • PostgreSQL 13.4, 13.6, 14.1, 15.x, 16, and 17

  • Enterprise Database (EDB) 15.x, 16

  • Fujitsu Enterprise PostgreSQL 15 SP2

  • AlloyDB Omni 15.5.x

ODBC driver requirement:

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, edb-odbc-16.00.0000.01

Supported target cloud databases and platforms

Oracle Cloud Infrastructure

Oracle Compute (IaaS) Virtual Machines and Bare Metal

Amazon Web Services

  • Amazon RDS for PostgreSQL
  • Amazon Aurora
  • Amazon EC2 (IaaS) Virtual Machine

Microsoft Azure

  • Azure Virtual Machine (IaaS)
  • Azure DBaaS

Google Cloud Platform

  • Cloud SQL for PostgreSQL

  • AlloyDB for PostgreSQL

Supported data types

SharePlex supports the following data types for replication from Oracle to PostgreSQL:

Oracle PostgreSQL
BINARY_DOUBLE DOUBLE PRECISION
BINARY_FLOAT REAL
CHAR (n) CHAR (n)
CHAR (n CHAR) CHAR (n)
CLOB TEXT
DATE DATE
DATE TIMESTAMP (0)
LONG TEXT
NCHAR (n) CHAR (n)
NCLOB TEXT
NUMBER

NUMERIC / DOUBLE PRECISION

NUMBER(p) NUMERIC (p)
NUMBER (p,s) NUMERIC (p,s)
NVARCHAR2 (n) VARCHAR (n)
TIMESTAMP (7:9) TIMESTAMP (6)
TIMESTAMP (p) TIMESTAMP (p)
TIMESTAMP (7:9) WITH TIME ZONE TIMESTAMP (6) WITH TIME ZONE
TIMESTAMP (p) WITH TIME ZONE TIMESTAMP (p) WITH TIME ZONE
TIMESTAMP (7:9) WITH LOCAL TIME ZONE TIMESTAMP (6)
TIMESTAMP (p) WITH LOCAL TIME ZONE TIMESTAMP (p)
VARCHAR2 (n) VARCHAR (n)
VARCHAR2 (n CHAR) VARCHAR (n)
BLOB BYTEA

Supported operations and objects for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to a PostgreSQL target. For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL replication

SharePlex supports DDL operations on tables and sequences, with some conditions. DDL can be replicated from an Oracle source to a PostgreSQL target. For additional information, see Oracle to open target DDL support.

Oracle to Snowflake replication

SharePlex supports replication from Oracle to Snowflake, according to the details below.

Supported operating systems

SharePlex replicates remotely to Snowflake. Remote replication from the following operating systems is supported:

  • RHEL 7.x, 8.x, and 9.x

  • Oracle Linux 7.x, 8.x, and 9.x

  • Windows Server 2019 and 2022

Note: SharePlex Snowflake supports only the 64-bit version of the listed operating systems.

Supported target versions and ODBC requirements

Snowflake 8.38.2

ODBC driver requirement for Linux: Snowflake 3.1.4 and above

ODBC driver requirement for Windows: From Snowflake 3.1.4 to Snowflake 3.2 version

Supported target cloud platforms

Microsoft Azure

Supported data types

SharePlex supports the following data types for replication from Oracle to Snowflake:

Oracle Snowflake
CLOB TEXT
NUMBER INT, INTEGER, NUMBER
CHAR(n) VARCHAR(n)
CLOB VARCHAR(n)
NCHAR CHAR(n)
VARCHAR2(n) VARCHAR(n)
CLOB VARCHAR(n)
NCLOB TEXT
CLOB VARCHAR(n)
LONG TEXT
BLOB BINARY, VARBINARY
RAW(n) VARBINARY
LONGRAW VARBINARY
BINARY_FLOAT REAL
NUMBER SMALLINT
NUMBER BIGINT
NUMBER NUMERIC, DECIMAL
DATE DATE
BINARY_DOUBLE DOUBLE PRECISION
TIMESTAMP TIMESTAMP
TIMESTAMP_TZ TIMESTAMP_TZ

Note: It is anticipated that the Snowflake DB's default "HEX" format for binary type will be maintained for Oracle binary to Snowflake binary data type replication. Since source Oracle DB binary data is stored only in "HEX" format, Shareplex does not guarantee data integrity for any other format.

Conditions of support
  • Char(n) data type - In Oracle, 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) Oracle 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 DB.

  • Binary & Text data types - Snowflake Binary & Text data types have size limitation of 8 MB, so Oracle’s advance Data type replication will be restricted to max 8 MB size limit of equivalent counterpart. Refer table below.

Oracle Data type Max Size Snowflake Data type Max Size
LONG 2 GB TEXT 8 MB of unicode chars
CLOB 4 GB TEXT 8 MB of unicode chars
LONGRAW 2 GB BINARY or VARBINARY 8 MB
BLOB 4 GB BINARY or VARBINARY 8 MB

See Conditions of support for the additional conditions of support for the above-mentioned supported data types.

Supported operations and objects for DML replication

SharePlex supports DML operations on tables, with some conditions. DML can be replicated from an Oracle source to a Snowflake target.

Tables

SharePlex supports the following DML operations on tables when replicating data from an Oracle 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 Oracle to Snowflake:

  • Slowness while performing DML operations

    • Single Insert: Frequent commits and rollbacks can cause slowness in replication.

    • Batch Inserts: Insert with advance data types [target Snowflake data types: TEXT and BINARY] can cause significant slowness in replication for data with plain text or binary JSON and XML.

    • Single Update and Delete : Frequent commits and rollbacks can cause slowness.

For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL replication

SharePlex does not support DDL operations and objects when replicating data from an Oracle source to a Snowflake target.

Oracle to SQL Server replication

SharePlex supports replication from Oracle to SQL Server, according to the details below.

Supported target operating systems

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 local installation:

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x, 8.x, and 9.x

  • Windows Server 2019 and 2022

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, 8.x, and 9.x

  • Windows Server 2019 and 2022

Supported target versions and ODBC requirements

SQL Server 2016, 2017, 2019, and 2022

ODBC driver requirement: ODBC 17.10.1.1-1 and 18.3.2.1-1

Supported target cloud platforms and databases

Amazon Web Services

Amazon EC2 (IaaS) Virtual Machine

Microsoft Azure

  • Azure Virtual Machine (IaaS)
  • Azure SQL Database
  • Azure SQL Managed Instance

Supported data types

SharePlex supports the following data types for replication from Oracle to SQL Server:

Oracle SQL Server
ANYDATA VARIENT
BINARY_DOUBLE FLOAT (53)
BINARY_FLOAT FLOAT (24)
BLOB VARBINARY (MAX)
CHAR (n) CHAR (n)
CHAR (n CHAR) CHAR (n)
CLOB VARCHAR (MAX)
DATE DATETIME2 (7)
LONG VARCHAR (MAX)
LONGRAW VARBINARY (MAX)
NCHAR (n) NCHAR (n)
NCLOB NVARCHAR (MAX)
NUMBER FLOAT (53)
NUMBER (p,0:) NUMERIC (p,s)
NUMBER (p,0:)* DECIMAL
NUMBER (p,s) FLOAT (53)
NVARCHAR2 (n) NVARCHAR (n)
RAW (n) VARBINARY (n)
TIMESTAMP (8:9) DATETIME2 (7)
TIMESTAMP (p) DATETIME2 (p)
TIMESTAMP (8:9) WITH TIME ZONE DATETIMEOFFSET (7)
TIMESTAMP (p) WITH TIME ZONE DATETIMEOFFSET (p)
VARCHAR2 (n) VARCHAR (n)
VARCHAR2 (n CHAR) VARCHAR (n)

Conditions of support:

NUMBER (P, 0) - DECIMAL: If we add a new column with the Number data type in the Oracle source, the new column will be replicated with the Numeric data type to the SQL Server target.

See Conditions of support for the additional conditions for the above-mentioned supported data types.

Supported operations and objects for DML replication

SharePlex supports DML operations on tables and sequences, with some conditions. DML can be replicated from an Oracle source to an SQL Server target. For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL replication

SharePlex supports DDL operations on tables and sequences, with some conditions. DDL can be replicated from an Oracle source to an SQL Server target. For additional information, see Oracle to open target DDL support.

System Requirements and Conditions of Support When Replicating from PostgreSQL

This chapter contains the requirements when capturing from a PostgreSQL database and replicating to supported target databases.

PostgreSQL source basics

This section contains the requirements for a PostgreSQL database as a source when capturing from a PostgreSQL database and replicating to supported target databases.

Supported operating systems

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 local installation

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x, 8.x, and 9.x

  • Ubuntu 22.04

Supported versions and ODBC requirements

  • PostgreSQL 13.x, 14.x, 15.x, 16, and 17

  • Enterprise Database (EDB) 15.x, 16

  • Fujitsu Enterprise PostgreSQL 15 SP2

  • AlloyDB Omni 15.5.x

ODBC driver requirement:

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

Supported cloud platforms and databases

Amazon Web Services:

  • Amazon EC2 (IaaS) Virtual Machine

  • Amazon RDS for PostgreSQL

  • Amazon Aurora

Microsoft Azure:

  • Azure Virtual Machine (IaaS)

  • Azure Flexible Server

Google Cloud Platform:

  • Cloud SQL for PostgreSQL

  • AlloyDB for PostgreSQL

PostgreSQL source basic conditions of support

Supported / non-supported SharePlex features for PostgreSQL as a source

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 PostgreSQL
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 Oracle
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 key1 PostgreSQL, Oracle, SQL Server, Kafka, Snowflake
Special characters2 PostgreSQL, Oracle, SQL Server, Kafka, Snowflake

Conditions of support:

  1. Data inconsistency is likely to occur in replication or compare-repair processes when SharePlex replication involves tables containing non-key columns with duplicate data.

  2. SharePlex supports special characters like hyphen (-), underscore (_), and plus (+) in PostgreSQL database names, as well as a dot (.), but other PostgreSQL objects, such as column names, do not support all special characters.

Supported and non-supported key features for physical and logical slots

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
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).

LIMITATIONS:

The following limitations are observed related to the TRUNCATE operation:

  • Applicable only for physical replication. If the truncate operation is performed on a table in replication, the Capture process ignores the DML operations performed on the table until the commit for the truncate operation is received or processed by the Capture process. Therefore, TRUNCATE should either be performed with auto-commit enabled or both TRUNCATE and COMMIT should be executed without any DML operations in between on the table.

  • Applicable only for logical replication. In bi-directional replication, the bulk delete operations performed immediately after a TRUNCATE operation are processed with some delay by the Capture processes. There is no data inconsistency once the bulk delete operations are processed.

PostgreSQL to Kafka replication

SharePlex supports replication from PostgreSQL to Kafka, according to the details below.

Supported operating systems

Supported operating systems via local 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.

Supported Kafka targets

  • Apache Kafka 3.6.1 and 3.8

  • Confluent Kafka 7.6

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.

Supported formats

XML format supported data types

SharePlex supports the following data types for replication from PostgreSQL to Kafka in XML format:

PostgreSQL Kafka (XML format)
SMALLINT Decimal
INT Decimal
BIGINT Decimal
REAL Decimal
DOUBLE PRECISION Decimal
NUMERIC Decimal
CHAR String
VARCHAR String
TEXT String
BYTEA Base64Binary
DATE DateTime
TIME Time
TIME WITH TIME ZONE Time
TIMESTAMP DateTime
TIMESTAMP WITH TIME ZONE DateTimeStamp
BOOLEAN String
JSON/JSONB String
JSON format supported data types

SharePlex supports the following data types for replication from PostgreSQL to Kafka in JSON format:

PostgreSQL Kafka (JSON format)
SMALLINT Number
INT Number
BIGINT Number
REAL Number
DOUBLE PRECISION Number
NUMERIC Number
CHAR String
VARCHAR String
TEXT String
BYTEA String containing base64 encoded data
DATE String containing date
TIME String containing time
TIME WITH TIME ZONE String containing time
TIMESTAMP String containing timestamp
TIMESTAMP WITH TIME ZONE String containing timestamp
BOOLEAN String
JSON/JSONB String

Supported DML operations

SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL source to a kafka target.

Tables

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

Supported operations and objects for DDL replication

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.

PostgreSQL to Oracle replication

SharePlex supports replication from PostgreSQL to Oracle, according to the details below.

Supported target operating systems

The following operating systems are supported from PostgreSQL to Oracle database. SharePlex supports only the 64-bit version of the listed operating systems.

Local SharePlex installation is supported on the below platforms:

  • AIX 7.3

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x, 8.x, and 9.x

  • RHEL 7.x, 8.x, and 9.x

  • CentOS Linux 7.x

  • Oracle Solaris SPARC 11.4

  • SuSE SLES 12.x and 15.x

  • Rocky Linux 8.x

  • Ubuntu 22.04

  • Windows 2019 and 2022*

*Note: Compare and Repair commands are not supported for PostgreSQL or Oracle on the Windows platform.

Remote replication from the following operating systems is supported:

  • AIX 7.3

  • HP-UX 11.31 Itanium

  • 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

  • Ubuntu 22.04

Supported target operating systems via remote replication:

All platforms listed above, plus Windows Server 2019 and 2022, are supported via remote replication.

Supported target database versions

Oracle 19c, 21c, and 23ai*

For detailed notes on the supported Oracle versions, see the Notes section under Supported target versions for Oracle-to-Oracle replication.

*Conditions of Support for Oracle 23ai:

  • Oracle 23ai is supported on DBCS, ExaCS/CC, and Oracle On-premises Exadata platforms.

  • On Oracle 23ai, the Copy/Append command is not supported with encrypted tablespaces.

Supported target cloud platforms

Oracle Cloud Infrastructure

  • Oracle Exadata Cloud Service (ExaCS)
  • Oracle Exadata Cloud@Customer (ExaCC)
  • Oracle Database Cloud Service (DBCS)
    • Enterprise Standard Edition

    • Enterprise Edition High Performance

    • Enterprise Edition Extreme Performance

  • Oracle Compute (IaaS) Virtual Machines and Bare Metal

For information on the conditions of support for Oracle Cloud Infrastructure, see the Conditions of support subsection added under Supported Target Cloud Platforms in the Oracle-to-Oracle replication section.

Amazon Web Services

  • Amazon RDS for Oracle
  • Amazon EC2 (IaaS) Virtual Machine

Microsoft Azure

Azure Virtual Machine (IaaS)

Supported characterset

UTF 8

Supported data types

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

Supported DML operations

SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL source to an Oracle target.

Tables

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.

Supported operations and objects for DDL replication

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.

PostgreSQL to PostgreSQL replication

SharePlex supports replication from PostgreSQL to PostgreSQL , according to the details below.

Supported target operating systems

Local SharePlex installation is supported on the following platforms:

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x, 8.x, and 9.x

  • Ubuntu 22.04

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, 8.x, and 9.x

  • Ubuntu 22.04

Supported target operating systems via remote replication:

  • AIX 7.3

  • CentOS Linux 7.x

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x, 8.x, and 9.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

  • Ubuntu 22.04

  • Windows Server 2019 and 2022

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Supported target versions and ODBC requirements

  • PostgreSQL 13.x, 14.x, 15.x, 16, and 17

  • Enterprise Database (EDB) 15.x, 16

  • Fujitsu Enterprise PostgreSQL 15 SP2

  • AlloyDB Omni 15.5.x

ODBC driver requirement:

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

Supported target cloud platforms

Amazon Web Services:

  • Amazon EC2 (IaaS) Virtual Machine

  • Amazon RDS for PostgreSQL

  • Amazon Aurora

Microsoft Azure:

  • Azure Virtual Machine (IaaS)

  • Azure Flexible Server

Google Cloud Platform:

  • Cloud SQL for PostgreSQL

  • AlloyDB for PostgreSQL

Supported characterset

UTF 8

Supported data types

SharePlex PostgreSQL supports the following data types for replication from PostgreSQL to PostgreSQL:

  • CHAR
  • VARCHAR
  • TEXT
  • SMALLINT
  • INT
  • BIGINT
  • NUMERIC
  • REAL
  • DOUBLE PRECISION
  • DATE
  • TIMESTAMP (0)
  • TIMESTAMP
  • TIMESTAMP WITH TIME ZONE
  • BOOLEAN
  • BYTEA
  • TIME
  • TIME WITH TIME ZONE
  • JSON
  • JSONB

Limitations:

  • The JSON & JSONB data types are supported only with logical replication.

  • Columns with the JSON and JSONB data types are not supported when defining a unique key.

  • Partition keys defined on JSON and JSONB data type columns are not supported for replicating partitioned table data.

  • A table containing columns with data types such as VARCHAR > 2k, VARCHAR without specified length, TEXT, BYTEA, JSON, and JSONB, without a defined key, and where basic data type columns are non-key columns with duplicate data across multiple rows, can result in data inconsistency during the Repair process.

Supported DML operations

SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL source to a PostgreSQL target.

Tables

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.

Supported operations and objects for DDL replication

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.

PostgreSQL to Snowflake replication

SharePlex supports replication from PostgreSQL to Snowflake, according to the details below.

Supported operating systems

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, 8.x, and 9.x

Supported target versions and ODBC requirements

Snowflake 8.38.2

ODBC driver requirement: Snowflake 3.1.4 and above

Supported target cloud platforms

Microsoft Azure

Supported data types

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
Conditions of support
  • 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

Supported operations and objects for DML replication

SharePlex supports DML operations on tables, with some conditions. DML can be replicated from an PostgreSQL source to a Snowflake target.

Tables

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:

  • Slowness while performing DML operations

    • Single Insert: Frequent commits and rollbacks can cause slowness in replication.

    • Batch Inserts: Insert with advance data types [target Snowflake data types: TEXT and BINARY] can cause significant slowness in replication for data with plain text or binary JSON and XML.

    • Single Update and Delete : Frequent commits and rollbacks can cause slowness.

For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL 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.

PostgreSQL to SQL Server replication

SharePlex supports replication from PostgreSQL to SQL Server, according to the details below.

Supported target operating systems

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 local 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, 8.x, and 9.x

Supported target operating systems via remote replication:

All platforms listed above, plus Windows Server 2019 and 2022, are supported via remote replication.

Supported target versions and ODBC requirements

SQL Server 2016, 2017, 2019, and 2022

ODBC driver requirement: ODBC 17.10.1.1-1 and 18.3.2.1-1

Supported target cloud platforms and databases

Amazon Web Services

Amazon EC2 (IaaS) Virtual Machine

Microsoft Azure

  • Azure Virtual Machine (IaaS)

  • Azure SQL Database

  • Azure SQL Managed Instance

Supported data types

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

Supported DML operations

SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL source to an SQL Server target.

Tables

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.

Supported operations and objects for DDL replication

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.

System Requirements and Conditions of Support When Replicating from PostgreSQL Database as a Service

This chapter contains the requirements when capturing from a PostgreSQL database and replicating to supported target databases.

PostgreSQL Database as a Service as source and target basics

SharePlex supports replication for the PostgreSQL Database as a Service as source, according to the details below.

Supported operating systems

Supported source operating systems via remote capture:.

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x, 8.x, and 9.x

  • Ubuntu 22.04

Supported target operating systems remote replication:

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x, 8.x, and 9.x

  • Ubuntu 22.04

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Supported cloud platforms and databases

Amazon Web Services:

  • Amazon RDS for PostgreSQL

  • Amazon Aurora

Microsoft Azure:

Azure Database for PostgreSQL Flexible Server

Google Cloud Platform:

  • Cloud SQL for PostgreSQL

  • Alloy DB

Note: PostgreSQL Database as a Service supports only logical replication.

Supported PostgreSQL versions

PostgreSQL 13.x , 14.x, 15.x, 16

ODBC driver requirement

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

Supported data types

  • CHAR

  • VARCHAR

  • SMALLINT

  • INT

  • BIGINT

  • NUMERIC

  • REAL

  • DOUBLE PRECISION

  • DATE

  • TIMESTAMP [p]

  • TIMESTAMP

  • TIMESTAMP [p] [WITH TIME ZONE]

  • TEXT

Supported DML operations

SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service as source to a PostgreSQL target.

Tables

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.

Supported operations and objects for DDL replication

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.

PostgreSQL Database as a Service to Kafka replication

SharePlex supports replication from PostgreSQL Database as a Service to Kafka, according to the details below.

Supported operating systems

Supported source operating systems via remote capture:

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • Oracle Linux 7.x, 8.x, and 9.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, 8.x, and 9.x

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Supported Kafka targets

  • Apache Kafka 3.6.1 and 3.8

  • Confluent Kafka 7.6

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.

Supported formats

Supported DML operations

SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service as source to a Kafka target.

Tables

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

Supported operations and objects for DDL replication

SharePlex does not support DDL operations and objects when replicating data from a PostgreSQL Database as a Service as source to a Kafka target.

PostgreSQL Database as a Service to Oracle replication

SharePlex supports replication from PostgreSQL Database as a Service to Oracle, according to the details below.

Supported target operating systems

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.

Local SharePlex installation is supported on the below platforms:

  • AIX 7.3

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x, 8.x, and 9.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

  • Ubuntu 22.04

Remote replication from the following operating systems is supported:

  • AIX 7.3

  • CentOS Linux 7.x

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x and 8.x

  • Oracle Solaris SPARC 11

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • SuSE SLES 12.x and 15.x

  • Ubuntu 22.04

Supported target operating systems via remote replication:

All platforms listed above, plus Windows Server 2019 and 2022, are supported via remote replication.

Supported target database versions

Oracle 19c, 21c, and 23ai*

For detailed notes on the supported Oracle versions, see the Notes section under Supported target versions for Oracle-to-Oracle replication.

*Conditions of Support for Oracle 23ai:

  • Oracle 23ai is supported on DBCS, ExaCS/CC, and Oracle On-premises Exadata platforms.

  • On Oracle 23ai, the Copy/Append command is not supported with encrypted tablespaces.

Supported target cloud platforms and databases

Oracle Cloud Infrastructure

  • Oracle Exadata Cloud Service (ExaCS)
  • Oracle Exadata Cloud@Customer (ExaCC)
  • Oracle Database Cloud Service (DBCS)
    • Enterprise Standard Edition

    • Enterprise Edition High Performance

    • Enterprise Edition Extreme Performance

  • Oracle Compute (IaaS) Virtual Machines and Bare Metal

For information on the conditions of support for Oracle Cloud Infrastructure, see the Conditions of support subsection added under Supported Target Cloud Platforms in the Oracle-to-Oracle replication section.

Amazon Web Services

  • Amazon RDS for Oracle
  • Amazon EC2 (IaaS) Virtual Machine

Microsoft Azure

Azure Virtual Machine (IaaS)

Supported characterset

UTF 8

Supported data types

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

Supported DML operations

SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service to an Oracle target.

Tables

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.

Supported operations and objects for DDL replication

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.

PostgreSQL Database as a Service to PostgreSQL replication

SharePlex supports replication from PostgreSQL Database as a Service to PostgreSQL, according to the details below.

Supported target operating systems

Local SharePlex installation is supported on the following platforms:

  • Oracle Linux 7.x, 8.x, and 9.x

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • Ubuntu 22.04

Remote replication from the following operating systems is supported:

  • Oracle Linux 7.x, 8.x, and 9.x

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

  • Ubuntu 22.04

Supported target operating systems via remote replication:

  • AIX 7.3

  • CentOS Linux 7.x

  • HP-UX 11.31 Itanium

  • Oracle Linux 7.x, 8.x, and 9.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

  • Ubuntu 22.04

  • Windows Server 2019 and 2022

Note: SharePlex supports only the 64-bit version of the listed operating systems.

Supported target versions and ODBC requirements

  • PostgreSQL 13.x , 14.x, 15.x, 16, and 17

  • Enterprise Database (EDB) 15.x and 16

  • Fujitsu Enterprise PostgreSQL 15 SP2

  • AlloyDB Omni 15.5.x

ODBC driver requirement:

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

Supported target cloud platforms and databases

Amazon Web Services:

  • Amazon EC2 (IaaS) Virtual Machine

  • Amazon RDS for PostgreSQL

  • Amazon Aurora

Microsoft Azure:

  • Azure Virtual Machine (IaaS)

  • Azure Flexible Server

Google Cloud Platform:

  • Cloud SQL for PostgreSQL

  • AlloyDB for PostgreSQL

Supported characterset

UTF 8

Supported data types

SharePlex PostgreSQL supports the following data types for replication from PostgreSQL Database as a Service to PostgreSQL:

  • CHAR
  • VARCHAR
  • TEXT
  • SMALLINT
  • INT
  • BIGINT
  • NUMERIC
  • REAL
  • DOUBLE PRECISION
  • DATE
  • TIMESTAMP (0)
  • TIMESTAMP
  • TIMESTAMP WITH TIME ZONE
  • BOOLEAN
  • BYTEA
  • TIME
  • TIME WITH TIME ZONE

Supported DML operations

SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service to a PostgreSQL target.

Tables

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.

Supported operations and objects for DDL replication

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.

PostgreSQL Database as a Service to Snowflake replication

SharePlex supports replication from PostgreSQL Database as a Service to Snowflake, according to the details below.

Supported operating systems

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:

  • Oracle Linux 7.x, 8.x, and 9.x

  • RHEL 7.x, 8.x, and 9.x

Supported target versions and ODBC requirements

Snowflake 8.38.2

ODBC driver requirement: Snowflake 3.1.4 and above

Supported target cloud platforms

Microsoft Azure

Supported data types

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
Conditions of support
  • 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.

Supported operations and objects for DML replication

SharePlex supports DML operations on tables, with some conditions. DML can be replicated from an PostgreSQL Database as a Service to a Snowflake target.

Tables

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:

  • Slowness while performing DML operations

    • Single Insert: Frequent commits and rollbacks can cause slowness in replication.

    • Batch Inserts: Insert with advance data types [target Snowflake data types: TEXT and BINARY] can cause significant slowness in replication for data with plain text or binary JSON and XML.

    • Single Update and Delete : Frequent commits and rollbacks can cause slowness.

For additional information, see Supported Operations and Objects for DML Replication.

Supported operations and objects for DDL 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.

PostgreSQL Database as a Service to SQL Server replication

SharePlex supports replication from PostgreSQL Database as a Service to SQL Server, according to the details below.

Supported target operating systems

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 local installation:

  • Oracle Linux 7.x, 8.x, and 9.x

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

Remote replication from the following operating systems is supported:

  • Oracle Linux 7.x, 8.x, and 9.x

  • RHEL 7.x, 8.x, and 9.x

  • Rocky Linux 8.x

Supported target operating systems via remote replication:

All platforms listed above, plus Windows Server 2019 and 2022, are supported via remote replication.

Supported target versions and ODBC requirements

SQL Server 2016, 2017, 2019 and 2022

ODBC driver requirement: ODBC 17.10.1.1-1 and 18.3.2.1-1

Supported target cloud platforms and databases

Amazon Web Services

Amazon EC2 (IaaS) Virtual Machine

Microsoft Azure

  • Azure Virtual Machine (IaaS)

  • Azure SQL Database

  • Azure SQL Managed Instance

Supported data types

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

Supported DML operations

SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service to an SQL Server target.

Tables

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.

Supported operations and objects for DDL replication

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.

Known issues

Known Issues in this Release

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
SPSQL-8730

In SPUtils Task Manager on Windows, the port for Sp_CopSvr is visible, but the port details for the SharePlex processes started by Sp_CopSvr are not displayed.

Workaround: Check for the SharePlex process connected to the specific port using sp_ctrl. This will display the processes associated with that port, showing their Cygwin PIDs. The corresponding Windows PIDs can be found using the ps command.

SPUtils/Windows
SPSQL-8734

The PIDs displayed for all SharePlex processes in the sp_ctrl Status command output do not match the PIDs shown in the SPUtils Task Manager tab.

Workaround: Execute the following command in the Command Prompt to view the Windows PID when the process is in a running state:

ps -W | findstr <cygwin_pid>

SPUtils Task Manager/Windows
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
SPSQL-8400

In the Compare/Repair process, the row count in the Oracle table might be outdated because it is initially fetched from the system table sys.tab$, which is not updated in real-time and depends on the DB stats analyzer process. As a result, users may encounter the error source vs target table size difference too large incorrectly in some cases.

Workaround: Either wait for the row count to be updated in the system table by the stats analyzer process, or use the override option as suggested.

Compare/Repair
SPSQL-4858 SharePlex displays the ORA-22990: LOB locators cannot span transactions error, and Compare results show out-of-sync data when users perform DML operations on data in replication after moving a LOB segment. This issue occurs during 23ai batch execution. Compare
SPSQL-5664 The Copy command fails on Windows machines due to the ORACLE_HOME environment variable not being populated correctly. Copy command
SPSQL-4971 The tables are going out of sync after performing DML operations through otest, and the CLOB column data is not being inserted during the script execution. DML operations
SPSQL-5274 SharePlex displays incorrect column names for schemas when the column name exceeds 30 characters on the source, in JSON and XML formats, during replication from Oracle to Kafka. Kafka
SPSQL-4764 The Poster process fails to replicate data from Oracle 19c to the file target after a Truncate operation is performed on the replicated data. This issue specifically affects tables containing BFILE and SDO_GEOMETRY columns. 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-8303 The Poster process stops due to an error after activation when a partial wildcard in the config file matches both SharePlex demo tables and user-created tables. Poster
SPSQL-8404

The Poster process stops with an error when users try to replicate a horizontally partitioned table with a case-sensitive schema, table name, and a single partitioning scheme from the Oracle to the PostgreSQL database.

Workaround: Create separate partitioning schemes for each target table name and create a separate entry for each table in the config file.

Poster
SPSQL-8415 The Snowflake Poster encounters a core dump issue when calling SQLDriverConnect from OdbcDriver::connect() for Snowflake connections. It also fails when running the snowflake_cleansp utility during a function call. This issue is observed with ODBC driver version 3.3 and above. Poster
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-5630 The Poster process stops due to an error when only the target table has a check constraint, and the inserted data violates that check constraint. Poster
SPSQL-5454 The SharePlex Poster process stops after activating the configuration for a hash partition on a target VM that has a '-' in its hostname. This issue is observed on the Windows platform. Poster
SPSQL-5459 When inserting the same rows multiple times into a table without a primary key and then updating all rows, an OOS (out-of-sync) error message appears in the Poster log. This issue occurs for both tables with normal names and table names longer than 30 characters during Oracle to PostgreSQL replication. Poster
SPSQL-6117 The undo_provision utility is not fully reverting all the changes made by the Provision utility. Provision
SPSQL-5894 When the Capture, Export, and Post queues have messages, and users run the Purge Config command, all queues are emptied as expected. However, error messages are observed in the source event logs. Purge Config
SPSQL-5550 When using the Query command 'job status "Error"', the status history for previous jobs with the "Error" status is not shown during Oracle to Oracle and PostgreSQL to PostgreSQL replication. Query command
SPSQL-8019

SharePlex displays the error index row size 3040 exceeds btree version 4 maximum 2704 when users set the parameter SP_DEQ_USE_SP_CKSUM=1 and try to repair a table without a Primary Key (PK) during Oracle to PostgreSQL replication.

Workaround:

  1. Ensure that the table has a valid Primary Key (PK) or Unique Key (UK).

  2. Set the parameter SP_DEQ_USE_SP_CKSUM=0 and exclude columns of type LONG, BINARY_FLOAT, BINARY_DOUBLE, and NUMBER without precision during the Compare/Repair process.

Repair
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-16453 The BINARY_FLOAT and BINARY_DOUBLE data types are not supported for the copy command. Character Sets
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-20843 Copy job status shows 'Locked' even when competed. Copy/ Append
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
SPSQL-8632 The Copy command executes successfully, but when checking the status with the Job Status command, it displays Syncing instead of Done. Job Status
SPSQL-8407

During Oracle to Kafka replication, the schema records of all tables are being replicated, not just the tables being replicated from Oracle to Kafka.

Workaround: Set the schema value to 'no' to avoid sending the schema record. However, validate whether the schema record is used internally before applying this setting.

Kafka
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-20842 On Oracle 19c processing large n-items can lead to OOS and/or missing commits. LOBs, VARRAYs, XML
SPO-22342 Performance issue is observed while performing the DML operations in bulk. MySQL
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
SPO-22517 Performance issue is observed during replication while using partition table over the cloud. Partition table
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-4982 The SharePlex Poster process displays the Poster: execute select pg_replication_origin_create ('sp_post_xxxx_x'); failed error when creating an origin with logical replication for PostgreSQL to PostgreSQL replication. Poster
SPSQL-5252 The SharePlex Poster stops due to an error when attempting to resolve conflicts on VARCHAR columns in a PostgreSQL-Oracle bi-directional setup using a user-defined conflict resolution procedure. Poster
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-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
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. varray columns

Third-party known issues

Issue ID Known Issue Component/ Feature
29865658 On Windows Server, Oracle 19c versions below 19.6 have an Oracle bug (29865658) that causes the SharePlex ora_setup, Reader, and Poster processes to get stuck. This bug is fixed in version 19.6 and later.To avoid this issue with SharePlex, either upgrade the Oracle 19c database to version 19.6 or higher. Users need to contact Oracle to obtain a patch for bug 29865658 or set the CLIENT_STATISTICS_LEVEL database parameter to 'OFF'. Oracle
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
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación