Chatee ahora con Soporte
Chat con el soporte

SharePlex 10.2 - Release Notes

Basic system requirements

This chapter contains the basic system requirements for SharePlex. See also: Source and Target System Requirements and Data Types

System

Before installing SharePlex, ensure that your system meets the minimum hardware and software requirements.

  • SharePlex processes are all 64-bit and can exceed 4 GB.
  • Per process memory of greater than or equal to 256 MB is required. Depending on how you configure SharePlex, there can be one or more of the following processes on a system :
    • Capture
    • Read
    • Export
    • Import
    • Post
  • See the Preinstallation Checklist in the SharePlex Installation Guide for additional system and/or database requirements.

Communications Protocols

SSL/TLS

For TLS connections, SharePlex supports TLS 1.2 (or later) only.

Internet Protocol

SharePlex supports IPv4 and IPv6 internet protocols. The following table shows the operating systems for which SharePlex was tested with IPv6.

Note: If the SP_SYS_HOST_NAME environment variable is set to an IPV6 address on the source system, SharePlex on the target system must be version 9.0 or later.

Operating System

Source

Target

SharePlex Source
and Target versions

On-premises/Cloud

Linux RHEL

Link-Local IPV6

Link-Local IPV6

9.0 - 9.0

On-premises

Linux RHEL

Link-Local IPV6

Link-Local IPV6

8.6.5 - 9.0

On-premises

Linux RHEL

Link-Local IPV6

Link-Local IPV6

9.0 - 8.6

On-premises

Linux Suse

Link-Local IPV6

Link-Local IPV6

9.0 - 9.0

On-premises

Windows

Link-Local IPV6

Link-Local IPV6

9.0 - 9.0

On-premises

Windows

Link-Local IPV6

Link-Local IPV6

9.0 - 8.6.4

On-premises

HP UA

Link-Local IPV6

Link-Local IPV6

9.0 - 9.0

On-premises

HP IA

Link-Local IPV6

Link-Local IPV6

9.0 - 9.0

On-premises

SUN Sparc

Link-Local IPV6

Link-Local IPV6

9.0 - 9.0

On-premises

SUN Solaris

Link-Local IPV6

Link-Local IPV6

9.0 - 9.0

On-premises

AIX

Link-Local IPV6

Link-Local IPV6

9.0 - 9.0

On-premises

Linux RHEL

Public IPV6

Public IPV6

9.0 - 9.0

Cloud

Windows

Public IPV6

Public IPV6

9.0 - 9.0

Cloud

Interoperability between versions

Refer to the following guidelines if the system where you are installing SharePlex is in a configuration where one or more other systems will continue to use an older version of SharePlex. An example is when installing or upgrading SharePlex on a target, but the source will continue to use SharePlex 8.6.x.

Versions with full interoperability

The following SharePlex versions are fully interoperable, including the Compare/Repair feature:

  • 8.6.x
  • 9.0.x
  • 9.1.x
  • 9.2.x
  • 9.4.x
  • 10.0.x
  • 10.1.x

To support replication from a higher to a lower version, set the SP_SYS_TARGET_COMPATIBILITY parameter on the source system to the lower SharePlex version. If Capture is running, restart it.

Important: Downgrading from a higher to a lower version of SharePlex is not supported.

Notes:

  • The older version of the SP_SYS_TARGET_COMPATIBILITY parameter, SP_OCT_TARGET_COMPATIBILITY, was deprecated in version 9.0. If your source SharePlex is currently replicating to a lower SharePlex version on the target and you have SP_OCT_TARGET_COMPATIBILITY set to the lower version, SharePlex will continue to use that value after you upgrade to the current version.
  • If you upgrade the target to the current release at a future time, issue a reset for SP_OCT_TARGET_COMPATIBILITY on the source system to remove it from the SharePlex environment. Going forward, SharePlex will use the setting of the new SP_SYS_TARGET_COMPATIBILITY parameter, which defaults to the current version.

    To reset SP_OCT_TARGET_COMPATIBILITY

    1. Stop Capture.

      sp_ctrl> stop capture

    2. In sp_ctrl on the source system, issue the following command:

      sp_ctrl>reset param SP_OCT_TARGET_COMPATIBILITY

    3. Restart Capture.

      sp_ctrl>start capture

Source and Target System Requirements and Data Types

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

Prerequisite: 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 and Target

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

Supported Operating Systems for Oracle

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 Oracle Source and Target Versions.

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

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.1 and 7.2
  • CentOS Linux 5.x, 6.x, and 7.x, and 8.x
  • Oracle Linux (RHCK and UEK) 5.x, 6.x, and 7.x, and 8.x
  • RHEL 5.x, 6.x, and 7.x, and 8.x

  • SuSE SLES 11.x, 12.x, and 15.x
  • Oracle Solaris SPARC 10.0, 11.0, and 11.4*
  • Oracle Solaris x86 10.0 and 11.4*
  • Windows Server 2008, 2008 R2, 2012, 2012 R2, and 2016, and 2019
  • HP-UX 11.31 Itanium
  • IaaS (Infrastructure as a Service) support - Azure and AWS

Note: *SharePlex supports remote replication for the Solaris 11.3 platform when the database is running on Solaris 11.3 and SharePlex is on a Linux platform.

Supported Cloud Platforms for Oracle

Oracle Cloud Infrastructure

  • Oracle Exadata Cloud Service (ExaCS)
  • Oracle Exadata Cloud@Customer (ExaCC)1
  • Oracle Database Cloud Service (DBCS)
  • Oracle Compute (IaaS) Virtual Machines and Bare Metal

Amazon Web Services

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

Microsoft Azure

Azure Virtual Machine (IaaS)

Condition of support

1. Conditions of support - ExaCC

Issues on Oracle Exadata Cloud@Customer will be tested against Oracle Exadata Cloud Service for reproduction purposes.

2. Conditions of support - Amazon RDS for Oracle

Please see Supported Oracle Source and Target Versions for additional clarification on version compatibility.

Supported Oracle Source and Target Versions

SharePlex supports the Standard and Enterprise Editions of Oracle 11gR2, 12cR1, 12cR2, 18c, and 19c.

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 Oracle Exadata Database Machine.
  • Amazon RDS for Oracle 11gR2 (supported 11gR2 versions are 11.2.0.4.v11 or later), 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-11-2, default:oracle-ee-12-1, default:oracle-ee-19 & default:oracle-se2-19.

Supported Data Types: Oracle to Oracle

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

PostgreSQL Target

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

Supported Operating Systems for PostgreSQL

The following operating systems are supported for PostgreSQL Server database. SharePlex supports only the 64-bit version of the listed operating systems.

Native SharePlex installation is supported on the below platforms:

  • RHEL 7.x and 8.x

  • IaaS (Infrastructure as a Service) support - Azure and AWS

Replication can be supported on the below platforms using Remote Post from Linux:

Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016, and 2019

Supported Cloud Platforms for PostgreSQL

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

Supported Database Versions for PostgreSQL

PostgreSQL 9.4, 9.5, 9.6, 10, 13.4, and 14.0

ODBC driver requirement: pgsql-14

Supported Data Types: Oracle to PostgreSQL

How to Read the Supported Data Types Table/Grid

This section contains information about the supported data types grid that can be read vertically and horizontally to understand how SharePlex supports replication between an Oracle source and the various Open Target targets (non-Oracle targets) that SharePlex supports.

  • Column 1: Shows the Oracle data types that SharePlex can replicate to an Open Target target type (non-Oracle target).
  • Column 2: Shows the native data types that SharePlex supports for each target type.

  • Rows spanning Column 1 and Column 2: Shows the default data type mapping (native Oracle data type to native target data type) that SharePlex uses when replicating Oracle ALTER TABLE...ADD COLUMN DDL operations. Post uses the specified native target data type in the column definition of the command on the target. The default mapping is what was tested and is supported.

Oracle PostgreSQL
BINARY_DOUBLE DOUBLE PRECISION
BINARY_FLOAT REAL
CHAR (n) CHAR (n)
CHAR (n CHAR) CHAR (n)
CLOB TEXT
DATE DATE
LONG TEXT
NCHAR (n) CHAR (n)
NCLOB TEXT
NUMBER NUMERIC
NUMBER (p,0:) NUMERIC (p,s)
NUMBER (p,s) NUMERIC
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)
Conditions of support

See Supported Data Types: Oracle to Oracle for additional conditions of support for Oracle source data types.

SQL Server Target

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

Supported Operating Systems for SQL Server

The following operating systems are supported for SQL Server database. SharePlex supports only the 64-bit version of the listed operating systems.

Native SharePlex installation is supported on the below platforms:

  • RHEL 7.x and 8.x

  • IaaS (Infrastructure as a Service) support - Azure and AWS

Replication can be supported on the below platforms using Remote Post from Linux:

Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016, and 2019

Supported Cloud Platforms for SQL Server

Amazon Web Services

Amazon EC2 (IaaS) Virtual Machine

Microsoft Azure

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

Supported Database Versions for SQL Server

SQL Server 2008, 2008 R2, 2012, 2014, 2016, 2017, and 2019.

ODBC driver requirement:

  • Microsoft ODBC Driver 17 for SQL Server
  • Microsoft ODBC Driver 18 for SQL Server

NOTES:

  • The SQL Server database is supported on RHEL and Windows server operating systems.
  • Azure SQL Database and SQL Server database are supported on RHEL 7.x and Windows Server 2016 & 2019 as a remote post.

Supported Data Types: 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,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)

Note: To understand how to read the above grid/table, see How to read the supported data types table/grid.

Conditions of support

See Supported Data Types: Oracle to Oracle for additional conditions of support for Oracle source data types.

MySQL Target

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

Supported Operating Systems for MySQL

The following operating systems are supported for MySQL Server database. SharePlex supports only the 64-bit version of the listed operating systems.

Native SharePlex installation is supported on the below platforms:

  • RHEL 7.x and 8.x

  • IaaS (Infrastructure as a Service) support - Azure and AWS

Replication can be supported on the below platforms using Remote Post from Linux:

Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016, and 2019

Supported Cloud Platforms for MySQL

Amazon Web Services

  • Amazon RDS for MySQL
  • Amazon Aurora

Microsoft Azure

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

Supported Database Versions for MySQL

MySQL 5.5, 5.6, 5.7, and 8

ODBC driver requirement: MySQL ODBC Drivers 8.0.26 for Linux

Supported Data Types: 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) 2 DATETIME (6)
TIMESTAMP (p) 2 DATETIME (p)
VARCHAR2 (n) VARCHAR (n)

Note: To understand how to read the above grid/table, see How to read the supported data types table/grid.

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.
  2. If the MySQL target database is earlier than version 5.6.4, the fractional seconds will be truncated. Earlier versions did not support fractional seconds.

See Supported Data Types: Oracle to Oracle for additional conditions of support for Oracle source data types.

Hana Target

SharePlex for Hana is in limited support effective February 1, 2022. SharePlex supports replication from Oracle to HANA, according to the details below.

Supported Hana Targets

SAP HANA 1.0 SPS 11

Supported Data Types: Oracle to HANA

Oracle HANA
BINARY_DOUBLE DOUBLE
BINARY_FLOAT DOUBLE
BLOB BLOB
CHAR (n) CHAR (n)
CLOB CLOB
DATE TIMESTAMP
LONG CLOB
LONGRAW BLOB
NCHAR (n) NCHAR (n)
NCLOB NCLOB
NUMBER DECIMAL
NUMBER (p,0:) DECIMAL (p,s)
NUMBER (p,s) DECIMAL
NVARCHAR2 (n) NVARCHAR (n)
RAW (n) VARBINARY (n)
TIMESTAMP (p) TIMESTAMP
VARCHAR2 (n) VARCHAR (n)

Note: To understand how to read the above grid/table, see How to read the supported data types table/grid.

Conditions of support

See Supported Oracle Source and Target Versions for additional conditions of support for Oracle source data types.

Kafka Target

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

Supported Kafka Targets

Apache Kafka 0.8.x, 0.9.x, 0.10.x, 0.11.x, 1.0.x, 1.1.x, 2.0.x, 2.1.0, 2.3.1, 2.5.0, and 3.0

Supported File Types

Supported Platforms

Linux: When replicating data to the Kafka (Apache and Confluent) target, target SharePlex should be installed only on the Linux platform.

 

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.

Azure Event Hubs Target

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

Supported Azure Event Hubs Target

Supported message queue: Azure Event Hubs

Supported File Types

JMS Message Queues Target

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

Supported JMS Message Queues

  • JMS - Apache ActiveMQ 5.8
  • JMS - IBM MQ 8

Supported File Types

File Output Target

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

Supported File Types

  • XML file
  • SQL file
  • JSON file

XML Supported Data Types

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.

Note: To understand how to read the above grid/table, see How to read the supported data types table/grid.

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 Supported Oracle Source and Target Versions for additional conditions of support for Oracle source data types.

JSON Supported Data Types

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

Note: To understand how to read the above grid/table, see How to read the supported data types table/grid.

Conditions of support

See Supported Data Types: Oracle to Oracle for additional conditions of support for Oracle source data types.

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 datatypes to ensure successful DML operations.
  • If the precision or size of the target datatype 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 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 target or an Open Target 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 for an Oracle Source.

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

Supported Operations and Objects for DDL replication

SharePlex provides default and optional DDL support.

Note: Support for DDL on compressed Oracle objects is limited to the following:

  • SharePlex supports DDL on compressed objects only for Oracle 11gR2 and later source Oracle databases.
  • 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'.

Oracle-to-Oracle DDL Support

This section outlines both default and optional DDL support.

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.
  2. For CREATE TABLE AS SELECT, SharePlex supports the following datatypes: LONG, DATE, RAW, LONG RAW, ROWID, LONG VARCHAR, CHAR, CLOB, BLOB, CFILE, BFILE, TIMESTAMP, INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND and ANYDATA.

  3. For CREATE MATERIALIZED VIEW the following applies:

    • SharePlex supports the following datatypes 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 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.

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

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

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

Oracle to Open Target DDL support

SharePlex provides limited DDL support for replication from Oracle to Open Target. 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 Open Target.

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:

  1. TRUNCATE TABLE is not supported from Oracle compressed objects to Open Target targets.

  2. The default mappings of Oracle data types to their Open Target counterpart for replicated ALTER TABLE ADD COLUMN DDL is shown in Supported Operating Systems for Oracle . When SharePlex adds the column, it defines it with the default data type. This mapping applies to the entire configuration (not per table).

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

Supported / non-supported SharePlex Features for Open Targets

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

SharePlex feature Supported for Open Target Not Supported for Open Target
reconcile command (target instantiation) X  
compare/compare using and repair/repair using commands   X
copy/copy using and append/append using commands   X
Hash horizontally partitioned replication   X
Column-based horizontally partitioned replication X  
Vertically partitioned replication X  
Column mapping X  
Key definition X  
Build configuration with scripts   X
Named queues X  
Commit Reduction (feature of Post Enhanced Performance) X  
Dependency Checking (feature of Post Enhanced Performance)   X
Transformation   X
Conflict resolution   X
Peer-to-peer replication (bi-directional)   X
Consolidated replication (many to one) X  
Broadcast replication (one to many) X  
High availability replication (active/passive bi-directional)   X
Change tracking target (CDC)   X
Data encryption X  
Data compression X  
SSH X  
auth_hosts file X  
Monitoring scripts X  
SNMP monitoring X  
Continue posting on error (SP_OPX_CONT_ON_ERR) X  
Suspend on out of sync errors (SP_OPX_OUT_OF_SYNC_SUSPEND) X  
Reduced key (SP_OPX_REDUCED_KEY) X  
Logical Transaction Rollback on out-of-sync transactions   X

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.

NOTE: For OLTP, SharePlex supports the following operating systems only.

  • AIX 7.1 and 7.2
  • Oracle Linux (RHCK and UEK) 5.x, 6.x, and 7.x
  • RHEL Linux 5.x, 6.x, and 7.x
  • CentOS Linux 5.x, 6.x, and 7.x
  • Oracle Solaris SPARC 11.4

Non-supported Operating Systems

  • Windows operating system

    Note: OLTP patch for the Windows operating system is not available from Oracle. Oracle has planned to release it in July 2021.

Supported Oracle Database Version/s

SharePlex supports Oracle 19c database version for replicating the OLTP compressed data.

Known issues

Known Issues in this Release

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

PostgreSQL known issue
Known Issues Issue ID

While running the pg_setup utility, if users encounter the "file not found" problem on a Linux system , even though the file is present. This issue occurs because the SharePlex has upgraded the OpenSSL library and the PostgreSQL ODBC drivers continue to function with the older version of OpenSSL.

Workaround: Create a symbolic links to the OpenSSL libraries of SharePlex in the <prod>/lib directory.

For example: The symbolic link libcrypto.so.1.0.0 will point to libcrypto.so.1.1 and the symbolic link libssl.so.1.0.0 will point to libssl.so.1.1.

Commands:

ln -s libcrypto.so.1.1 libcrypto.so.1.0.0

ln -s libssl.so.1.1 libssl.so.1.0.0

SPO-22799

SQL Server known issue

Known Issues Issue ID
SharePlex Poster is displaying the ODBC Driver Invalid precision value error when replicating the BLOB data type with the data size of more than 8000 bytes. SPO-24119
MySQL known issue
Known Issues Issue ID
Performance issue is observed while performing the DML operations in bulk. SPO-22342
PostgreSQL and MySQL known issue
Known Issues Issue ID
Performance issue is observed during replication while using partition table over the cloud. SPO-22517

Remote Post Linux known issues

Known Issues Issue ID

Poster stops when users enable an encryption key for the export/ import process while replicating data using remote post.

This issue is observed on the Linux server.

 SPO-22081

 

SQL Server known issues

DDL Drop Column known issue
Known Issues Issue ID

While activating a config file with an Oracle SCN number, users are not able to delete a column in a DDL activity.

 SPO-21993
General known issues
Known Issue Issue ID
The reported core file was not generated on systems running Oracle 11g on the SunOS, and Linux operating systems. 66306
If the customer issues an "ALTER TABLE ... MOVE COMPRESS" DDL command against a table in replication, SharePlex will replicate the DDL to the target by default. After post issues the DDL, if the target table had indexes, they are now unusable and post will subsequently fail trying to apply changes to the table. If post gets an error on the table such as "ORA-01502: index XXX or partition of such index is in unusable state" , the user must rebuild any indexes the table may have before restarting post in order to rectify the situation. N/A
SharePlex copy is not supported for tables created with "MAPPING TABLE" clause. SPO-19626
Windows known issues
Known Issue Issue ID
On Windows systems, the uninstaller does not prompt for the version of SharePlex to be removed from a system. When there are multiple versions of SharePlex installed on a system, it removes only the first installation. N/A
In the Windows environment, always run sp_ctrl from the same drive on which you have installed SharePlex. If you run sp_ctrl from another drive, you will be prompted for a login ID and password. After you provide the login ID and password, sp_ctrl will run normally. N/A
If the user wants to change the installation directory for a given port, the user must first uninstall from the previous location. Note that if the user wants to keep the previous VARDIR it should be copied to the new location prior to the uninstall. 62620
Installing on Windows 2019 as Windows Administrator user will cause sp_wallet and qview to fail. Workaround: Set NUT_TREAT_ADMINS_AS_ROOT environment variable to 1 for the Windows Administratoruser before starting any SharePlex utilities or applications. SPO-20785
During installation when upgrading from 9.2.x it is possible to get a file not found error in the PTC NuTCRACKER Platform Components.
Workaround: Rename or remove the mks_oe directory under the SharePlex installation directory before upgrading.		 SPO-20910
ASM known issues
Known Issue Issue ID
If the redo_log or archive_log that SharePlex is currently reading is involved in “rebalancing” due to the removal of a disc group, the Capture process will pause until the rebalance procedure for that file is complete. N/A
On raw device ASM systems, the sp_desvr may get stuck and the process can not be killed even when kill -9 is issued; users must reboot the system to recover from it. 61713
Startup known issues
Known Issue Issue ID

If you have SharePlex configured to start from a startup script and it returns an error similar to: System call error: sp_cnc (connecting from cdrpx.mcit.med.umich.edu) Bad file number Can't dup2 stderr try adding nohup to your script. The nohup command directs a command (in this case the startup of SharePlex) to continue in the background after the current user (the script) logs out. The syntax is:

cd /product_directory/bin

nohup ./sp_cop &

N/A
Character Sets known issues
Known Issue Issue ID

Avoid replicating NCHAR data types using different character sets such as AL16UTF16 on the source machine and UTF8 on the target due to byte size limitations. Oracle stores NCHAR data with a maximum limit of 2000 bytes. A fixed length NCHAR character set such as AL16UTF16 has a different maximum number of characters than a variable length NCHAR character set such as UTF8. For the fixed length AL16UTF16 character set, each character is stored as 2 bytes; thus, the maximum number of characters is 1000 for NCHAR data. For the variable length UTF8 character set, the maximum number of characters a column can accommodate depends on how many bytes each character requires. If you replicate 1000 3-byte characters from a source machine using the AL16UTF16 character set to a target machine set to UTF8, you will get the following Oracle error message on the target, since it needs 3000 bytes:

ORA-01461 can bind a LONG value only for insert into a LONG column

35198
compare known issues
Known Issue Issue ID

If the compare command specifies a WHERE clause that includes a column name containing one or more spaces, the spaces are removed in the WHERE clause in the query used in the comparison causing the comparison to fail.

 N/A
A compare of a partition can't be done if the partition is an Oracle hash partition. The compare can still be done on the whole table or with a specified where clause. SPO-20141
Compare/Repair using [schema].[table] may not work on AIX7.2 with Oracle19c due to establishing a network connection. SPO-20451
Compare will hang and the compare server will exit comparing table that has VARRAY containing UDT type. SPO-20733

 

Copy/ Append known issues
Known Issue Issue ID
If you need to copy a materialized view to a table, you should drop the target table before copying. Please be aware that the new target table created by copy will have an additional column named M_ROW$$ which does not exist on the source. The use of append on a materialized view to a table is not supported. 41679
The BINARY_FLOAT and BINARY_DOUBLE data types are not supported for the copy command. SPO-16453
Copy job status shows 'Locked' even when competed. SPO-20843
Conflict Resolution known issues
Known Issue Issue ID
The !ControlExtendedCharSet prepared conflict resolution routine and the !DEFAULT parameter currently cannot be used for generic conflict resolution. N/A
Partitioned Replication known issues
Known Issue Issue ID
When using a compound routing map in a placeholder route in the configuration file, do not use spaces between each routing component. For example, sysb@o.orab+sysc@o.oraC is correct because there are no spaces before or after the + symbol. N/A
Post will fail with ORA-14400 performing DML on partitioned table with VARAY residing in an OLTP compressed tablespace. SPO-20841
Capture known issue
Known Issues Issue ID
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. SPO-21339
 
Vertical and Horizontal Partitioning known issues
Known Issue Issue ID
When using horizontal partition replication with DATE data type in the column condition, the DATE needs to follow the SP date string format, 'MMDDSYYYYHH24MISS'. Otherwise, the Read and Compare processes are not able to process it. 55268
   

 

LOBs, VARRAYs, and XML known issues
Known Issue Issue ID
Users may encounter an out-of-sync condition when an UPDATE occurs on a table that contains a UDT with a VARRAY column, and there is no KEY on the table. This issue is specific to Solaris x86 operating systems. 29650
On Oracle 19c processing large n-items can lead to OOS and/or missing commits. SPO-20842

 

DDL Replication known issues
Known Issue Issue ID
Replicating CREATE ROLE (set param SP_OCT_REPLICATE_ALL_DDL 1) is changing the grantee name on the target to the name of the SharePlex Administrator. 2242
If the Capture process is behind in reading the Oracle redo or archive logs when the SP_OCT_REPLICATE_ALL_DDL parameter is enabled it will replicate DDLs whose time stamps precede this event. 56957
In replication from an Oracle source to a non-Oracle target, SharePlex does not support ALTER TABLE to add a number column in which the scale is larger than the precision. SPO-14372
In replication from an Oracle source to a non-Oracle target, SharePlex does not support ALTER TABLE...ADD COLUMN DDL operations when the column name is more than 30-bytes in length.

SPO-15585

 

Partition DDL known issues
Known Issue Issue ID
If separate SQL statements for partition DDL and index rebuild are run on the source, SharePlex only replicates the partition DDL and leaves target global index unusable. This is because ALTER INDEX is not supported by SharePlex. The recommended work around is that all partition DDLs which mark global indexes as unusable should be run with an appending clause UPDATE GLOBAL INDEXES to the ALTER TABLE SQL statements. The alternative is to manually rebuild the global indexes on target. 57939

 

Function based index known issues
Known Issue Issue ID
If there is more than one function defined in the index, SharePlex will choose the first. SharePlex cannot support multiple functions. 92931

 

Post to JMS known issues
Known Issue Issue ID

Replication of batch operations to ActiveMQ may cause a hang. The workaround is to set the SP_ORD_BATCH_ENABLE parameter to 0.

SPO-11335

If the post process that is writing to JMS is not on the same machine as the source database, and if the two machines are of different endianness, NCHAR data will not be written to JMS correctly. 107471

 

Post to non-Oracle targets known issues
Known Issue Issue ID

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.

SPO-19048

Oracle Compression known issues
Known Issue Issue ID
Oracle 19c OLTP Compression. SharePlex does not support replication of DML operations on objects compressed using OLTP Compression in Oracle 19c. SPO-19793
Hybrid Columnar Compression. Activation will not fail if a table with “COMPRESS FOR QUERY LOW” compression is activated. Capture will log a message indicating that “COMPRESS FOR QUERY LOW” is not supported. 107487
Oracle 18c OLTP Compression. SharePlex does not support replication of DML operations on objects compressed using OLTP Compression in Oracle 18c. SPO-16449

Third-party known issues

Third-party known issues: Linux
Known Issue Issue ID
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. 54799
Third-party known issues: Oracle
Known Issue Issue ID
There is an Oracle issue that can cause SharePlex Capture to fail when replicating the OLTP compressed table that is having a column name with more than 30 characters. This is a known Oracle issue addressed under Oracle Bug 31776789. SPO-23856
There is an Oracle issue that can cause SharePlex Poster to fail when replicating the OLTP compressed table that is having a column with more than 30 characters. This is a known Oracle issue addressed under Oracle Bug 31786282. SPO-23509
Oracle may allow an invalid date, such as year 0000, to be inserted as the key value of a table without generating an error. This causes SharePlex to return an “Invalid DATE format detected in record with rowid” error when trying to insert the record to the target. SPO-1368
Users wishing to employ IOTs with overflow need to be running Oracle 11g or higher. This is a known Oracle issue addressed under Oracle Bug 4627859. 44626
On Windows systems, the Post process May exit when it encounters an "ORA-07445: exception encountered: core dump" error. Please refer to Oracle Bug 6658912 for more information and the Oracle provided work around. 67441
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. 75179
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. 92152
Sometimes the Post process will hang updating a SecureFile LOB. For more information please refer to Oracle tar SR 3-2898230851: OCILobWrite hangs at the OCI_LAST_PIECE for securefile LOB. N/A
There is an Oracle bug that can cause the database to crash when supplemental logging is enabled and transactions involving tables in a compressed tablespace are rolled back. Please refer to Oracle bug 8331063 for more information. N/A
A known issue in PL/SQL prevents the SharePlex conflict resolution logic from compiling the PL/SQL for tables whose names are the same as their owners. Oracle has stated that the issue will not be fixed. See Oracle TAR 2577886.996 for more information. This issue does not affect replication; SharePlex supports tables with identical owner and table names. N/A
Third Party Known Issues: Misc
Known Issue Issue ID
When replicating data from Oracle to SQL Server, the Microsoft SQL Server ODBC driver supports Owner names of up to 127 bytes only. SPO-14331
A known issue in EDB Postgres ODBC driver prevents support for emoji UTF-8 character set with EDB Postgres target. SPO-15251

Product Licensing

Licensing

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

To activate a trial license

  2. Run the SharePlex command:

    ./splex_add_key 

    SharePlex License Utility
1) Read license key from file
2) Enter license key manually
3) Add license key for alternate host
q) Quit License Utility
Enter option:
  3. Enter option 2.
  4. Enter the key provided in the email from Quest Licensing.
  5. For the customer name, enter: Trial Version.

To activate a purchased commercial license

  2. Run the SharePlex command:

    ./splex_add_key 

    SharePlex License Utility
1) Read license key from file
2) Enter license key manually
3) Add license key for alternate host
q) Quit License Utility
Enter option:

  3. Enter option 2.

  4. Enter the key provided in the email from Quest Licensing.

  5. Enter the customer name provided in that email.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación