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

SharePlex 12.1 - Release Notes

Oracle to File Output replication

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

Supported target operating systems

For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section.

Supported file types

  • XML file
  • SQL file
  • JSON file
  • Parquet file*

* Note: The Parquet file type is supported only on Linux platforms.

Limitation: 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 File Output.

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.

Parquet format supported open targets
Oracle Parquet Logical Type Parquet Physical Type
CHAR STRING BYTE_ARRAY with UTF-8 encoding
VARCHAR / VARCHAR2 STRING BYTE_ARRAY with UTF-8 encoding
NUMBER(p) DECIMAL(p) FIXED_LEN_BYTE_ARRAY
NUMBER(ps) DECIMAL(p, s) FIXED_LEN_BYTE_ARRAY
NUMBER DECIMAL(38, 18) FIXED_LEN_BYTE_ARRAY
BINARY_FLOAT / BINARY_DOUBLE DOUBLE DOUBLE
DATE TIMESTAMP (milliseconds / seconds) INT64
TIMESTAMP([0-3]/[4-6]/[7-9]) TIMESTAMP (milliseconds / microsecond/ nanosecond) INT64
TIMESTAMP with TZ TIMESTAMP (milliseconds / microsecond/ nanosecond) INT64
TIMESTAMP with LTZ TIMESTAMP (milliseconds / microsecond/ nanosecond) INT64
CLOB / NCLOB STRING BYTE_ARRAY with UTF-8 encoding
LONG / LONGVARCHAR STRING BYTE_ARRAY with UTF-8 encoding
BLOB BINARY BYTE_ARRAY
RAW / LONGRAW BINARY BYTE_ARRAY

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. SharePlex does not support DDL replication from Oracle to a Parquet file. 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

For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section.

Supported JMS Message Queues

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

Supported file types

Limitation: 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 JMS Message Queues.

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

Oracle to Kafka replication

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

Supported target operating systems

For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section. To view compatibility across operating systems for remote replication, see Compatibility Across Operating Systems (Remote Collection and Posting).

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

Limitation: 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.

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

For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section. To view compatibility across operating systems for remote replication, see Compatibility Across Operating Systems (Remote Collection and Posting).

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.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation