Chat now with support
サポートとのチャット

SharePlex 9.2.5 - Release Notes

Basic system requirements

This chapter contains the basic system requirements for SharePlex. See also:

System Requirements for Oracle Capture

System Requirements for SQL Server Capture

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

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

System requirements for Oracle

System Requirements for Oracle Capture

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

Prerequisites
  • At least the minimum level of supplemental logging must be enabled. Some SharePlex features may require PK/UK supplemental logging to be enabled.

Supported Operating Systems

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

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

Note:  SharePlex supports the following operating systems only.

  • AIX 7.1 and 7.2
  • CentOS Linux 5.x, 6.x, and 7.x
  • HP-UX 11.31 Itanium
  • Oracle Linux (RHCK and UEK) 5.x, 6.x, and 7.x
  • RHEL Linux 5.x, 6.x, and 7.x
  • SuSE SLES 11.x, 12.x, and 15
  • Oracle Solaris (SPARC and x86) 10 and 11
  • Windows Server 2008, 2008 R2, 2012, 2012 R2, and 2016

Supported Source and Target Databases

When capturing from an Oracle database and replicating to an Oracle or other database, the following database types and versions are supported for source and target.

NoteS:

  • Unless specified, Oracle, RAC, and ASM are supported for the same version.
  • SharePlex supports only the 64-bit version of Oracle Database.
Supported Oracle Sources Supported Targets

Supported versions

  • Oracle 11gR2, 12cR1, 12cR2, 18c

    These Oracle versions are also supported when running on Oracle Exadata

Supported versions for a cloud-based source:3

  • 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) 2

    Note: Support for Oracle features on Amazon RDS is limited to the default option groups: default:oracle-ee-12-1 and default:oracle-ee-11-2.

  • Oracle 11gR2, 12cR1, 12cR2, 18c on an Amazon EC2 virtual machine or Microsoft Azure IaaS

 

Supported database types and versions:

  • Oracle 11gR2, 12cR1, 12cR2, 18c

    These Oracle versions are also supported when running on Oracle Exadata

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

    NOTE: The SQL Server database is supported only on the Windows Server operating system.

  • MySQL 5.5, 5.6, 5.7
  • PostgreSQL 9.4, 9.5, 9.6, and 10
  • EDB Postgres Advanced Server 9.4, 9.5, 9.6, and 101
  • Fujitsu Enterprise Postgres 9.5
  • SAP Adaptive Server Enterprise (ASE) 15.7
  • SAP HANA 1.0 SPS 11
  • Teradata 15.00, 15.10
  • Tibero 6.0

Supported message queues:

  • JMS - Apache ActiveMQ 5.8
  • JMS - IBM MQ version 8
  • Apache Kafka 0.8.x, 0.9.x, 0.10.x, 0.11.x, 1.0.x, 1.1.x

Supported file types:

  • XML, SQL, and JSON files

Supported database types and versions for a cloud-based target:

  • Amazon Aurora PostgreSQL-Compatible Edition
  • Amazon Aurora MySQL-Compatible Edition
  • Amazon RDS for Oracle, SQL Server, MySQL, and PostgreSQL. 2  For supported versions, see Supported database types and versions above.

  • Oracle Cloud Infrastructure as a Service (IaaS) Compute Virtual Machine is supported for Oracle-to-Oracle replication
  • Databases listed in Supported database types and versions above are also supported when they are deployed on an Amazon EC2 virtual machine, Microsoft Azure IaaS, or Microsoft Azure PaaS2.

Table Notes:

  1. SharePlex does not support CESU-8 data replication to EDB Postgres Advanced Server 10.

  2. In Microsoft Azure PaaS or Amazon RDS, SharePlex cannot be installed because there is no access to the underlying operating system. You must install SharePlex on a different server. You then configure SharePlex to interact with the target database through a remote connection. Because the connection originates locally, use the target database ODBC driver that matches the local server.

  3. Capture from an Oracle database deployed on Microsoft Azure Platform as a Service (PaaS) is not supported.

Additional Requirements

Requirement Details

ODBC Driver

For the following supported target databases, the applicable ODBC driver is required. Use the ODBC driver and version recommended by the vendor.

  • SQL Server
  • MySQL
  • PostgreSQL
  • EDB Postgres Advanced Server
  • SAP Adaptive Server Enterprise (ASE)
  • Teradata
  • Fujitsu Enterprise Postgres

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

    See "Database Setup for PostgreSQL" in the SharePlex Installation and Setup Guide for an Oracle Source for detailed instructions.

Java Runtime Environment (JRE) for JMS

A compatible JRE is required for replication to JMS. OpenJDK is included in the SharePlex installation, with the following exceptions.

  • OpenJDK is not included when SharePlex is installed in the following operating systems. For the following systems, ensure a compatible JRE, version 1.8 (or later), is pre-installed.
    • CentOS Linux 5.x
    • Oracle Linux 5.x
    • RHEL Linux 5.x

Supported data types: Oracle to Oracle

SharePlex supports the following Oracle data types for replication to Oracle targets. See the Conditions of suppport 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
  • RAW
  • ROWID
  • SDO_GEOMETRY
  • TIMESTAMP
  • TIMESTAMP WITH LOCAL TIME ZONE
  • TIMESTAMP WITH TIME ZONE
  • UDT (User Defined Type)5
  • UROWID
  • VARCHAR
  • VARCHAR2
  • VARRAY collectors
  • XMLTYPE 4

Conditions of suppport

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

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

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

6. Conditions of support - 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 the BINARY FLOAT

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

Supported data types: Oracle to Open Target

This section contains a 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.

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.

Oracle to HANA supported data types

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

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

Oracle to MySQL supported data types

See "Conditions of support" following this table for additional information.

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)

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.
  3. See Supported data types: Oracle to Oracle for additional conditions of support for Oracle source data types.

Oracle to PostgreSQL supported data types

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.

Oracle to SAP ASE supported data types

Oracle SAP ASE
BINARY_DOUBLE FLOAT
BINARY_FLOAT FLOAT
BLOB IMAGE
CHAR (n) CHAR (n)
CLOB TEXT
DATE DATETIME (p)
LONG TEXT
LONGRAW IMAGE
NUMBER NUMERIC
NUMBER (p,0:) NUMERIC (p,s)
NUMBER (p,s) NUMERIC
RAW (n) VARBINARY (n)
VARCHAR2 (n) VARCHAR (n)
Conditions of support

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

Oracle to SQL Server supported data types

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

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

Oracle to Teradata supported data types

Oracle Teradata
CHAR (n) CHAR (n)
DATE TIMESTAMP (0)
NUMBER NUMBER
NUMBER (p, 0:) NUMBER (p, s)
NUMBER (p, s) NUMBER
VARCHAR2 (n) VARCHAR (n)
Conditions of support

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

Oracle to Tibero supported data types

Oracle Tibero
BINARY_DOUBLE BINARY_DOUBLE
BINARY_FLOAT BINARY_FLOAT
BLOB BLOB
CHAR (n) CHAR (n)
CLOB CLOB
DATE DATE
INTERVAL DAY TO SECOND INTERVAL DAY TO SECOND
INTERVAL YEAR TO MONTH INTERVAL YEAR TO MONTH
LONG LONG

LONGRAW

LONG RAW

NCHAR (n) NCHAR (n)

NCLOB

NCLOB

NUMBER NUMBER
NUMBER (p,s) NUMBER (p,s)
NVARCHAR2 (n) NVARCHAR (n)
RAW (n) RAW (n)
ROWID ROWID
TIMESTAMP (p) TIMESTAMP (p)
TIMESTAMP (p) WITH LOCAL TIME ZONE TIMESTAMP (p) WITH LOCAL TIME ZONE
TIMESTAMP (p) WITH TIME ZONE TIMESTAMP (p) WITH TIME ZONE
VARCHAR2 (n) VARCHAR2 (n)
Conditions of support

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

Oracle to XML supported data types

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

  • File in XML format
  • JMS
  • Kafka

See "Conditions of support" following this table for additional information.

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

  1. 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)
  2. See Supported data types: Oracle to Oracle for additional conditions of support for Oracle source data types.

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

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, OLTP, HCC3

All target types  

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

All target types  

Conditions of support

1. Conditions of support - TDE

SharePlex supports Tablespace Encryption and Column Encryption for Oracle 11g R2 and later versions, both source and target.

The SharePlex  copy/append command does not support TDE.

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.

3. Conditions of support - compression

Under certain conditions, Oracle does not provide enough information in the redo log for SharePlex to replicate a DML operation on a compressed object. Testing of 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, OLTP, and HCC compressed Oracle objects for replication to all Oracle and Open Target 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

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

Yes

SP_OCT_REPLICATE_DDL=3

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

Create

Create as Select2

Drop

Yes

SP_OCT_AUTOADD_ENABLE=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_MV=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 data types: Oracle to Open Target. 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 Target

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 (except Teradata)  
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 SQL Server

System Requirements for SQL Server Capture

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

SharePlex support for SQL Server as a target is documented in "Set up replication from Oracle to SQL Server" in the SharePlex Installation and Setup Guide for Oracle Source.

Supported Operating Systems

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

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

Notes:

  •  SharePlex supports the following operating systems only.
  • The SQL Server database is supported only on the listed Windows operating systems.

Supported Operating Systems for Source

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

Supported Operating Systems for Target

  • AIX 7.1 and 7.2
  • CentOS Linux 5.x, 6.x, and 7.x
  • HP-UX 11.31 Itanium
  • Oracle Linux (RHCK and UEK) 5.x, 6.x, and 7.x
  • RHEL Linux 5.x, 6.x, and 7.x
  • SuSE SLES 11.x, 12.x, and 15
  • Oracle Solaris (SPARC and x86) 10 and 11
  • Windows Server 2008, 2008 R2, 2012, 2012 R2, and 2016

Supported Source and Target Databases

When capturing from a SQL Server database and replicating to a target database, the following database types and versions are supported for source and target.

Supported SQL Server Sources Supported Targets

Supported versions

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

Supported versions for a cloud-based source:3

  • SQL Server 2008, 2008 R2, 2012, 2014, 2016, 2017 on an Amazon EC2 virtual machine or Microsoft Azure IaaS.

 

Supported database types and versions:

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

    NOTE: The SQL Server database is supported only on the Windows Server operating system.

  • Oracle 11gR2, 12cR1, 12cR2, 18c

    These Oracle versions are also supported when running on Oracle Exadata

  • MySQL 5.5, 5.6, 5.7
  • PostgreSQL 9.4, 9.5, 9.6, and 10
  • EDB Postgres Advanced Server 9.4, 9.5, 9.6, and 10 1

Supported message queues:

  • Apache Kafka 0.8.x, 0.9.x, 0.10.x, 0.11.x, 1.0.x, 1.1.x

Supported database types and versions for cloud-based target:

  • Amazon Aurora PostgreSQL-Compatible Edition
  • Amazon Aurora MySQL-Compatible Edition
  • Amazon RDS for SQL Server. 2  For supported versions, see Supported database types and versions above.

  • Databases listed in Supported database types and versions above are also supported when they are deployed on Amazon EC2, Microsoft Azure IaaS, or Microsoft Azure PaaS2.

Table Notes:

  1. SharePlex does not support CESU-8 data replication to EDB Postgres Advanced Server 10.

  2. In Microsoft Azure PaaS or Amazon RDS, SharePlex cannot be installed because there is no access to the underlying operating system. You must install SharePlex on a different server. You then configure SharePlex to interact with the target database through a remote connection. Because the connection originates locally, use the target database ODBC driver that matches the local server.

  3. Capture from a SQL Server database deployed on Microsoft Azure Platform as a Service (PaaS) or in Amazon RDS is not supported.

Additional Requirements

Requirement Details
ODBC Driver

For the following supported target databases, the applicable ODBC driver is required. Use the ODBC driver and version recommended by the vendor.

  • SQL Server
  • MySQL
  • PostgreSQL
  • EDB Postgres Advanced Server

Conditions of support

This section shows the limitations of capturing from a SQL Server source.

  • SQL Server native replication and SharePlex replication cannot be used at the same time for the same database.
  • All SQL Server tables in the SharePlex replication configuration must be defined in the database with a primary key. A SharePlex key definition is not sufficient, nor can SharePlex use all columns as a key. You can use SharePlex filtering features in the configuration file to omit tables that do not have a primary key.
  • A transaction must COMMIT to the SQL Server source before it can be captured by SharePlex.
  • Replication between tables in same database is not supported. Replication between tables in different databases in the same or another SQL Server instance is supported.

Supported operations

  • SharePlex supports only DML replication from SQL Server to any of the supported targets.
  • SharePlex does not support the replication of SQL Server DDL operations.

The DML operations supported are: INSERT, UPDATE, and DELETE operations between SQL Server source tables and supported target tables that contain supported column types.

Notes:

  • SharePlex only replicates DML changes that are made to SQL Server source objects that are listed in the configuration file.
  • SharePlex requires SQL Server Replication to be installed on the source system. See the SharePlex Installation Guide for more information.

Supported data types: SQL Server to SQL Server

SharePlex supports DML operations between SQL Server databases that contain the following SQL Server data types:

  • bigint
  • binary(n)
  • bit
  • char(n)
  • date
  • datetime
  • datetime2(p)
  • datetimeoffset(p)
  • float(p)
  • image
  • integer 1
  • money
  • nchar(n)
  • ntext
  • numeric(p,s)
  • nvarchar(n)
  • real
  • smalldatetime
  • smallint
  • text
  • time(p)
  • tinyint
  • uniqueidentifier
  • varbinary(n)
  • varchar(n)

NOTEs:

  1. Integer column with Identity property: In addition to the Integer data type, an Integer column with the Identity property assigned to it is also supported.

Supported data types: SQL Server to Oracle and Open Target

The following tables show the supported data type mappings between a SQL Server source and a given Oracle or Open Target database. These are the mappings that have been tested and are known to be successful across a variety of use cases. Mapping to unsupported data types may succeed but has not been tested.

SQL Server to Oracle supported data types

SQL Server Oracle

bigint

NUMBER

binary(n)

RAW (n)

bit NUMBER (1,s)
char(1:3999) CHAR (n)
char(4000:) CLOB

date

DATE

datetime TIMESTAMP (3)
datetime2(p) TIMESTAMP (p)
datetimeoffset(p) TIMESTAMP (p) WITH TIME ZONE
float(n) NUMBER
image BLOB

integer

NUMBER

money NUMBER
nchar(1:3999) NCHAR(n)
nchar(4000:) NCLOB
ntext NCLOB
numeric(p,s) NUMBER (p,s)
nvarchar(1:3999) NVARCHAR2 (n)
nvarchar(4000:) NCLOB

nvarchar(max)

NCLOB

real

NUMBER

smalldatetime

DATE

smallint

NUMBER

text CLOB

time(p)

DATE

tinyint

NUMBER

uniqueidentifier CHAR (36)
varbinary(n) RAW (n)

varbinary(max)

BLOB

varchar(1:3999) VARCHAR2 (n)
varchar(4000:) CLOB

varchar(max)

CLOB

SQL Server to MySQL supported data types

SQL Server MySQL

Notes

bigint BIGINT  
binary(1:255) BINARY (n)

 

binary(256:) LONGBLOB

 

bit TINYINT  
char(1:255) CHAR (n)

 

char(256:) LONGTEXT

 

date DATE

 

datetime DATETIME (0)

 

datetime2(p) DATETIME (p)

MySQL datetime supports up to 6 fractional digits, whereas SQL Server datetime2 supports up to 7 fractional digits.

float(n) FLOAT

 

image LONGBLOB

 

integer INTEGER

 

money NUMERIC (20,4)  
nchar(1:255) CHAR (n)

 

nchar(256:) LONGTEXT
ntext LONGTEXT
numeric(p,s) NUMERIC (p,s)

 

nvarchar(n)

VARCHAR (n)

The effective maximum length of a VARCHAR is subject to the maximum row size (65,535 bytes, which is shared among all columns) and the character set used.

nvarchar(max)

LONGTEXT

real

FLOAT

 

smalldatetime

DATETIME (0)

 

smallint

SMALLINT

 

text

LONGTEXT

 

time(p)

TIME (p)

 

tinyint

TINYINT

 

uniqueidentifier CHAR (36)  

varbinary(1:255)

VARBINARY (n)

 

varbinary(256:) LONGBLOB  

varbinary(max)

LONGBLOB

 

varchar(n)

VARCHAR (n)

The effective maximum length of a VARCHAR is subject to the maximum row size (65,535 bytes, which is shared among all columns) and the character set used.

varchar(max)

LONGTEXT

 

SQL Server to PostgreSQL supported data types

SQL Server PostgreSQL
bigint NUMERIC
bit BOOLEAN
char(n) CHAR(n)
date DATE
datetime TIMESTAMP(3)
datetime2(p) TIMESTAMP(p)
datetimeoffset(p) TIMESTAMP(p) WITH TIME ZONE
float(25:) DOUBLE PRECISION
float(1:24) REAL
integer INTEGER
money NUMERIC(20,4)
nchar(n) CHAR(n)
ntext TEXT
numeric(p,s) NUMERIC(p,s)
nvarchar(n) VARCHAR(n)
nvarchar(max) TEXT
real REAL
smalldatetime TIMESTAMP(0)
smallint SMALLINT
text TEXT
time(p) TIME(p)
tinyint SMALLINT
uniqueidentifier CHAR(36)
varchar(n) VARCHAR(n)
varchar(max) TEXT

SQL Server to Tibero supported data types

SQL Server Oracle

bigint

NUMBER

binary(n)

RAW(n)

bit NUMBER(1,s)
char(1:3999) CHAR(n)
char(4000:) CLOB

date

DATE

datetime TIMESTAMP(3)
datetime2(p) TIMESTAMP(p)
datetimeoffset(p) TIMESTAMP(p) WITH TIME ZONE
float(n) NUMBER
image BLOB

integer

NUMBER

money NUMBER
nchar(1:3999) NCHAR(n)
nchar(4000:) NCLOB
ntext NCLOB
numeric(p,s) NUMBER(p,s)
nvarchar(1:3999) NVARCHAR(n)
nvarchar(4000:) NCLOB

nvarchar(max)

NCLOB

real

NUMBER

smalldatetime

DATE

smallint

NUMBER

text CLOB

time(p)

DATE

tinyint

NUMBER

uniqueidentifier CHAR(36)
varbinary(n) RAW(n)

varbinary(max)

BLOB

varchar(1:3999) VARCHAR2(n)
varchar(4000:) CLOB

varchar(max)

CLOB

 

SQL Server to XML supported data types

SQL Server

XML

int

decimal

numeric

decimal

smallint

decimal

tinyint

decimal

float

decimal

real

decimal

date

dateTime

datetime

dateTime

datetime2

dateTime

datetimeoffset

dateTimeStamp

smalldatetime

dateTime

time

dateTime

char

string

nchar

string

text

coob

ntext

clob

nvarchar

string

binary

base64Binary

varbinary

base64Binary

image long

base64Binary

Supported SharePlex features

The following table shows whether or not SharePlex features are supported when SQL Server is the source.

SharePlex feature Supported with Oracle Target Supported with OpenTarget
Replication from SQL Server tables to any target where the version of SharePlex is earlier than 9.0. No No
Auto-add of new tables that satisfy a wildcard No No
flush command Yes Yes
reconcile command (target instantiation) Yes Yes
compare/compare using and repair/repair using commands No No
copy/copy using and append/append using commands No No
Hash horizontally partitioned replication No No
Column-based horizontally partitioned replication No No
Vertically partitioned replication Yes Yes
Column mapping Yes Yes
Key definition (SQL Server tables must have a defined key) No No
Build configuration with scripts No No
Named queues Yes Yes
Post Enhanced Performance No No
Transformation Yes No
Conflict resolution Yes No
Peer-to-peer replication (bi-directional) No SQL Server target only
Consolidated replication (many to one) Yes Yes
Broadcast replication (one to many) Yes Yes
Cascading replication (source-intermediary-target) Yes Yes
High availability replication (active/passive bi-directional) No No
Change history target (CDC) Yes No
Data encryption No No
Data compression No No
SSH No No
auth_hosts file No No
Monitoring scripts No No
SNMP monitoring No No
Continue posting on error (SP_OPX_CONT_ON_ERR) Yes Yes
Suspend on out of sync errors (SP_OPX_OUT_OF_SYNC_SUSPEND) Yes Yes
Reduced key (SP_OPX_REDUCED_KEY) Yes Yes
sp_ctrl commands See the command documentation in the Reference Guide. See the command documentation in the Reference Guide.
Logical Transaction Rollback on out-of-sync transactions Yes No

 

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.

SQL Server capture known issues
Known Issue Issue ID

If the source SQL Server version is 2012 and below, SharePlex will re-capture transactions that were already been processed if SharePlex is shut down ungracefully, either intentionally with a kill command or due to system failure. This results in double-posting on the target and resultant unique-constraint errors. To avoid these errors, always shut down SharePlex gracefully with the shutdown command in sp_ctrl before you shut down or reboot a system.

N/A

When replicating SQL Server datetimeoffset(0) to a target Oracle timestamp(0) with time zone column (only for precision 0), the timestamps will have incorrect timezone values in the Oracle target.

SPO-12155
When SP_OCT_REPLICATE_DDL is set to 3, SharePlex replicates DROP TABLE in addition to the commands that are documented as supported: ALTER TABLE (add, modify, drop column) and TRUNCATE TABLE.

SPO-13148

Binary collation is not supported for SQL Server capture to an Oracle target. SPO-15802

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

Oracle Compression known issues
Known Issue Issue ID
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
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
関連ドキュメント