This section contains information about SharePlex support for capture from an Oracle source database and replication to supported targets.
This section shows the SharePlex support for replication from source Oracle database-platform combinations to target database-platform combinations, both Oracle and Open Target.
NoteS:
Important: See also Cloud support for cloud-hosted targets.
Platform | Oracle source or target | |||||
---|---|---|---|---|---|---|
10g* |
10gR2* |
11g* |
11gR2* |
12cR1* |
12cR2* | |
AIX 5.3 | Yes | Yes | Yes | Yes | No | No |
AIX 6.1 | NA | Yes | Yes | Yes | Yes | No |
AIX 7.1 | NA | NA | NA | Yes | Yes | No |
CentOS 5.10 (x64) | NA | Yes | Yes | Yes | Yes | No |
CentOS 6.5 (x64) | NA | Yes | Yes | Yes | Yes | No |
Debian Release 8 (Jesse and Wheezy)*** | No | No | Yes | Yes | Yes | No |
HP-UX 11.31 (11i v3) (PA-RISC) |
Yes | Yes | Yes | Yes | NA | No |
HP-UX 11.31 (11i v3) (Itanium) |
Yes | Yes | Yes | Yes | Yes | No |
Oracle Solaris 9 | Yes | Yes | Yes | NA | NA | No |
Oracle Solaris 10 (SPARC) | Yes | Yes | Yes | Yes | Yes | No |
Oracle Solaris 10 (x64) | Yes | Yes | NA | Yes | Yes | No |
Oracle Solaris 11 (SPARC) | NA | NA | Yes | Yes | Yes | No |
Oracle Solaris 11 (x64) | NA | NA | Yes | Yes | Yes | No |
Oracle Linux 4 (x64) | Yes | Yes | Yes | Yes | NA | No |
Oracle Linux 5 (x64) | NA | Yes | Yes | Yes | Yes | No |
Oracle Linux 6 (x64) | NA | NA | NA | Yes | Yes | Yes |
Oracle Linux 7 (x64) | NA | NA | NA | Yes | Yes | Yes |
Oracle Linux 5 on Exadata 2, 3, 4 (x64) | NA | NA | NA | Yes | Yes | No |
Oracle Linux 5.5 on Exadata 3, 4 (x64) | NA | NA | NA | Yes | Yes | No |
Oracle Linux 6.6 on Exadata 5 (x64) | NA | NA | NA | Yes | Yes | No |
RHEL 4 (x64) | Yes | Yes | Yes | Yes | NA | NA |
RHEL 5 (x64) | NA | Yes | Yes | Yes | Yes | No |
RHEL 6 (x64) | NA | NA | NA | Yes | Yes | Yes |
RHEL 7 (x64) | NA | NA | NA | Yes | Yes | Yes |
SuSE SLES9 (x64) | Yes | Yes | NA | NA | NA | NA |
SuSE SLES10 (x64) | NA | Yes | Yes | Yes | NA | NA |
SuSE SLES11 (x64) | NA | Yes | Yes | Yes | Yes | No |
SuSE SLES12 (x64)** | NA | NA | NA | Yes | Yes | Yes |
Windows Server 2003 (x64) | NA | Yes | Yes | Yes | NA | NA |
Windows Server 2008 (x64) | NA | Yes | Yes | Yes | Yes | No |
Windows Server 2012 | NA | Yes | Yes | Yes | Yes | Yes |
Windows Server 2012R2 | NA | Yes | Yes | Yes | Yes | Yes |
NA: Not applicable: not supported by the database type or version.
X: Not yet tested.
* SharePlex only supports 64-bit Oracle Database. Linux running Oracle 11g must be running on Oracle 11.1.0.6.0+ or you must apply the one-off provided for Oracle Bug 6598432.
** At the time of this writing, Oracle’s published documentation did not indicate support of SuSE SLES12. Basic testing of SharePlex has been done on SuSE SLES12. Quest will provide best effort support but cannot resolve specific Oracle issues on this platform until Oracle adds official support.
*** Oracle does not officially support Debian Linux.
Important: See also Cloud support for cloud-hosted targets.
Platform* | Can post to target on this platform (Yes/No) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
MySQL |
SAP ASE |
SQL Server |
PostgreSQL** |
SAP HANA | Teradata |
JMS |
Kafka |
File | ||
AIX 6.1 | NA | NA | NA | NA | NA | NA | Yes | No | Yes | |
AIX 7.1 | NA | NA | NA | NA | NA | NA | Yes | No | Yes | |
CentOS 5.10 (x64) | NA | Yes | NA | NA | NA | NA | Yes | Yes | Yes | |
CentOS 6.5 (x64) | NA | Yes | NA | Yes | NA | NA | Yes | Yes | Yes | |
Debian Release 8 (Jesse and Wheezy) | NA | Yes | NA | Yes | NA | NA | Yes | Yes | Yes | |
HP-UX 11.31 (11i v3) (PA-RISC) |
NA | No | NA | NA | NA | NA | No | No | No | |
HP-UX 11.31 (11i v3) (Itanium) |
NA | No | NA | NA | NA | NA | No | No | No | |
Oracle Solaris 9 | NA | NA | NA | NA | NA | NA | NA | NA | NA | |
Oracle Solaris 10 (SPARC) | NA | NA | NA | NA | NA | NA | Yes | No | Yes | |
Oracle Solaris 10 (x64) | NA | NA | NA | NA | NA | NA | Yes | No | Yes | |
Oracle Solaris 11 (SPARC) | NA | NA | NA | NA | NA | NA | Yes | No | Yes | |
Oracle Solaris 11 (x64) | NA | NA | NA | NA | NA | NA | Yes | No | Yes | |
Oracle Linux 4 (x64) | No | NA | NA | No | NA | NA | Yes | Yes | Yes | |
Oracle Linux 5 (x64) | No | NA | NA | No | NA | NA | Yes | Yes | Yes | |
Oracle Linux 6 (x64) | No | NA | NA | No | NA | NA | Yes | Yes | Yes | |
Oracle Linux 7 (x64) | No | NA | NA | NA | NA | NA | Yes | Yes | Yes | |
Oracle Linux 5 on Exadata 2, 3, 4 (x64) | No | NA | NA | No | NA | NA | Yes | Yes | Yes | |
Oracle Linux 5.5 on Exadata 3, 4 (x64) | No | NA | NA | No | NA | NA | Yes | Yes | Yes | |
Oracle Linux 6.6 on Exadata 5 (x64) | No | NA | NA | No | NA | NA | Yes | Yes | Yes | |
RHEL 4 (x64) | Yes | Yes | NA | NA | NA | NA | Yes | Yes | Yes | |
RHEL 5 (x64) | Yes | Yes | NA | NA | NA | NA | Yes | Yes | Yes | |
RHEL 6 (x64) | Yes | Yes | NA | Yes | NA | NA | Yes | Yes | Yes | |
RHEL 7 (x64) | Yes | Yes | NA | Yes | NA | NA | Yes | Yes | Yes | |
SuSE SLES9 (x64) | Yes | Yes | NA | NA | Yes | NA | NA | Yes | NA | |
SuSE SLES10 (x64) | Yes | Yes | NA | NA | Yes | Yes (SP3) | Yes | Yes | Yes | |
SuSE SLES11 (x64) | Yes | Yes | NA | Yes | Yes | Yes (SP1) | Yes | Yes | Yes | |
SuSE SLES12 (x64)** | Yes | Yes | NA | NA | Yes | NA | Yes | Yes | Yes | |
Windows 2003 (x64) | NA | NA | Yes | NA | NA | NA | Yes | No | Yes | |
Windows 2008 (x64) | NA | NA | Yes | No | NA | NA | Yes | No | Yes | |
Windows Server 2012 | NA | NA | Yes | No | NA | NA | Yes | No | Yes | |
Windows Server 2012R2 | NA | NA | Yes | No | NA | NA | Yes | No | Yes |
* If a platform is not supported by a target type, it is not supported by SharePlex for that target type. For example, only R2 of Windows 2008 is supported by EDB Postgres Advanced Server, and therefore only by SharePlex.
** SharePlex supports all implementations of the PostgreSQL open source object-relational database system.For more information, see Basic system requirements.
SharePlex supports the following Oracle data types for replication to Oracle targets. See the Conditions of suppport for additional information.
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 datatypes within ANYDATA are supported by SharePlex:
2. Conditions of support - LONG and LOB (BLOB, CLOB)
Replication of SecureFile LOBs (compressed high or medium, or uncompressed) is supported as follows:
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 - VARRAYS
Only the following data types in a VARRAY are supported by SharePlex when replicating to XML output:
5. 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:
6. Conditions of support - general
When replicating DML operations to an Open Target database, SharePlex queries the target database to determine the target column definition before posting the data.
This section shows the following:
NOTES about open Target Data type support:
Oracle Data Type | Default mapping to HANA Data Type for DDL operations |
---|---|
BINARY_DOUBLE | double |
BINARY_FLOAT | double |
BLOB | blob |
CHAR | char |
CLOB | clob |
DATE | date |
LONG | clob |
LONGRAW | blob |
NCHAR | nchar |
NCLOB | nclob |
NUMBER | decimal |
NVARCHAR | nvarchar |
RAW | varbinary |
TIMESTAMP | timestamp |
VARCHAR/VARCHAR2 | varchar |
Conditions of support
Oracle Data Type | Default mapping to MySQL Data Type for DDL operations |
---|---|
BINARY_DOUBLE2 | double |
BINARY_FLOAT | double |
BLOB | longblob |
CHAR | char |
CLOB | longtext |
DATE | datetime |
LONG | text |
LONGRAW | blob |
NUMBER | numeric |
RAW | varbinary |
TIMESTAMP1 | datetime |
VARCHAR(2) | varchar |
Conditions of support
Oracle Data Type | Default mapping to PostgreSQL Data Type for DDL operations |
---|---|
BINARY_DOUBLE | double precision |
BINARY_FLOAT 1 | double precision |
CHAR | char |
CLOB | text |
DATE | date |
LONG | text |
NCHAR | char |
NCLOB | text |
NUMBER | numeric |
NVARCHAR | varchar |
TIMESTAMP | timestamp |
VARCHAR(2) | varchar |
Conditions of support
Oracle Data Type | Mapped to SAP ASE Data Type |
---|---|
BINARY_DOUBLE | float |
BINARY_FLOAT | float |
BLOB | image |
CHAR | char |
CLOB | text |
DATE | datetime |
LONG | text |
LONGRAW | image |
NUMBER | numeric |
RAW | varbinary |
VARCHAR(2) | varchar |
Conditions of support
See Supported data types — Oracle to Oracle for additional conditions of support for Oracle source data types.
Oracle Data Type | Default mapping to SQL Server Data Type for DDL operations |
---|---|
ANYDATA | sql_variant |
BINARY_DOUBLE | float |
BINARY_FLOAT | float |
BLOB | image |
CHAR | char |
CLOB | text |
DATE | datetime2 |
LONG | text |
LONGRAW | image |
NCHAR | nchar |
NCLOB | ntext |
NUMBER | numeric |
NVARCHAR | nvarchar |
RAW | varbinary |
TIMESTAMP WITH TIME ZONE | datetimeoffset |
TIMESTAMP | datetime2 |
VARCHAR(2) | varchar |
Conditions of support
See Supported data types — Oracle to Oracle for additional conditions of support for Oracle source data types.
Oracle Data Type | Default mapping to Sybase Data Type for DDL operations |
---|---|
BINARY_DOUBLE | float |
BINARY_FLOAT | float |
BLOB | image |
CHAR | char |
CLOB | text |
DATE | datetime |
LONG | text |
LONGRAW | image |
NUMBER | numeric |
RAW | varbinary |
VARCHAR(2) | varchar |
Conditions of support
See Supported data types — Oracle to Oracle for additional conditions of support for Oracle source data types.
Oracle Data Type | Default mapping to Teradata Data Type for DDL operations |
---|---|
CHAR | char |
DATE | timestamp |
NUMBER | number |
VARCHAR/VARCHAR2 | varchar |
Conditions of support
See Supported data types — Oracle to Oracle for additional conditions of support for Oracle source data types.
This mapping applies to all targets that receive messages as XML:
Oracle Data Type | Default mapping to XML Data Type for DDL operations |
---|---|
BLOB | base64Binary |
CHAR | string |
CLOB | string |
DATE | dateTime |
BINARY_FLOAT | decimal |
BINARY_DOUBLE | decimal |
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 TIME ZONE | dateTimeStamp |
TIMESTAMP WITH LOCAL 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
Only the following data types in a VARRAY are supported by SharePlex when replicating to XML output:
SharePlex supports DML replication from the following Oracle objects:
Any table can be replicated to an Oracle or non-Oracle target if the target supports all of the column types that are being replicated. This includes:
Notes:
The following table summarizes SharePlex DML support.
DML support | Supported for | |
---|---|---|
INSERT, UPDATE, DELETE, COMMIT, ROLLBACK on tables |
All target types | |
Direct-path loads (SQL*Loader) (INSERT AND FULL ROLLBACK) | All target types | |
DML on tables encrypted by Oracle Obfuscation Toolkit | All target types | |
DML on tables with TDE encryption1 |
All target types except Oracle 10g and 11gR1 | |
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 |
1. Conditions of support - TDE
2. Conditions of support - OLS
By default, SharePlex cannot process rows that are protected by OLS 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:
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.
SharePlex provides default and optional DDL support.
Notes:
ALTER TABLE to ADD COLUMN and ALTER TABLE to DROP COLUMN are supported on compressed source objects (Basic, OLTP, HCC) for all Oracle and Open Target targets.
Any object or operation not listed in one of the tables in this section is not supported for that feature.
This section shows the default DDL support for objects that are included in the active replication configuration either explicitly or with a wildcard.
The default Oracle-to-Oracle DDL configuration is controlled by the following parameter settings:
SP_OCT_REPLICATE_DDL=3 and
SP_OCT_AUTOADD_ENABLE=1 and
SP_OCT_REPLICATE_ALL_DDL=0
Supported object | Supported Operation |
---|---|
Table and IOT | Create table1 |
Create table as select1, 4 | |
Drop table1 | |
Create index1 | |
Drop index1 | |
Truncate2 | |
Alter table add column2 | |
Alter table drop column 2 | |
Comment on table2 | |
Comment on columns2 | |
Associate Statistics2 | |
Disassociate Statistics2 | |
Partition/ Subpartition2, 3 |
Add |
Split | |
Merge | |
Drop | |
Modify | |
Coalesce | |
Exchange | |
Move | |
Truncate | |
Rename | |
Set | |
Index1 | Create |
Alter | |
Drop |
Conditions of support
1. Enabled by default through SP_OCT_AUTOADD_ENABLE=1. Auto-Add automatically adds an object to replication if the name satisfies a wildcard in the active replication configuration.
2. Enabled by default through SP_OCT_REPLICATE_DDL=3. This is the default DDL support for objects that are listed in the active configuration.
3. The full default DDL support 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. If the database is earlier than Oracle 12.2, 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. This is not required for Oracle 12.2 or later and any setting is ignored.
Note: SharePlex does not support TRUNCATE of a system-generated sub-partition if the sub-partition is empty, and Post stops with error SP-OPO01002. To configure Post to ignore this error, set the SP_OPO_CONT_ON_ERR parameter to 1 and add error number SP-OPO01002 to the top of the oramsglist file, before you restart Post.
4. 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.
This section shows the default DDL support for Oracle objects when replicated to an Open Target, when the objects are included in the active replication configuration either explicitly or with a wildcard.
SharePlex only supports replication of TRUNCATE TABLE and ALTER TABLE to ADD COLUMN or DROP COLUMN to an Open Target database, file, or message container. No other DDL is supported to Open Target.
The default Oracle to Open Target configuration is controlled by the following parameters:
SP_OCT_REPLICATE_DDL=3 and
SP_OCT_AUTOADD_ENABLE=1 and
SP_OCT_REPLICATE_ALL_DDL=0
Supported object | Supported Operation |
---|---|
Table and IOT | Truncate1 |
Alter table add column2 | |
Alter table drop column |
1. Conditions of support - TRUNCATE TABLE
TRUNCATE TABLE is not supported from Oracle compressed objects to Open Target targets.
2. Conditions of support - data type mappings
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 Oracle. When SharePlex adds the column, it defines it with the default data type. This mapping applies to the entire configuration (not per table).
Note: These mappings are only used to establish column definitions for replicated ADD COLUMN operations. For replicated DML, SharePlex queries the target database to determine the appropriate data type to use.
Valid only for Oracle-to_Oracle replication
You can enable the replication of the following DDL with parameter settings when it is issued on objects that are in the configuration file.
DDL command | Parameter |
---|---|
CREATE / DROP TRIGGER | SP_OCT_REPLICATE_TRIGGER=1 |
CREATE / DROP SYNONYM | SP_OCT_REPLICATE_SYNONYM=1 |
GRANT | SP_OCT_REPLICATE_GRANT=1 |
Valid only for Oracle-to_Oracle replication
Optional Auto-Add support enables newly created materialized views and sequences to be added to replication automatically if the name of the object satisfies a wildcard in the active configuration file. It is configured as follows:
Materialized Views:
SP_OCT_AUTOADD_ENABLE=1 and
SP_OCT_AUTOADD_MV=1 and
SP_SYS_TARGET_COMPATIBILITY=8.6.2 or higher
Sequences:
SP_OCT_AUTOADD_ENABLE=1 and
SP_OCT_AUTOADD_SEQ=1 and
SP_SYS_TARGET_COMPATIBILITY=8.6.3 or higher
Notes:
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.
DDL support for objects not listed in the configuration file is valid only for Oracle-to-Oracle replication. SharePlex replicates the DDL statements, but does not replicate any data change operations made to the objects because they are not part of active replication. The expanded DDL configuration is controlled by the following parameter setting:
SP_OCT_REPLICATE_ALL_DDL=1
NoteS:
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 | |
Directory | 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 | |
Grant | |
Revoke | |
Role | Create role |
Alter role | |
Drop role | |
Grant | |
Revoke |
This is a list of commonly used Oracle components that SharePlex does not replicate. Since both Oracle and SharePlex continually change and improve, this list of exclusions cannot be considered complete. Unless explicitly stated that an item is supported, you should assume that SharePlex does not replicate it.
Object/operation/feature | Not supported |
---|---|
Tables and Objects | Replication of nested tables |
Replication of clustered tables | |
Replication of Index-Organized Tables with any of the following:
| |
Replication from a Non-IOT to an IOT table | |
Replication from materialized views to materialized views. (However, SharePlex replicates the underlying table of a materialized view to a target table.) | |
DDL operations | ANALYZE TABLE and ANALYZE INDEX |
DDL operation performed by a SharePlex Oracle user, if SP_OCT_REPLICATE_ALL_DDL is set to 1 | |
DDL to ALTER TABLE ADD OVERFLOW to an IOT in replication | |
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. |
Replication of partial rollbacks of DLOADs | |
Rows changed by 'UPDATE WITH CASE' syntax | |
SharePlex transformation and conflict resolution | LONG and LONG_RAW datatypes in a configuration where transformation or conflict resolution are performed |
Abstract datatypes and VARRAYs in a configuration where conflict resolution is performed | |
SharePlex horizontal partitioning | SharePlex horizontal partitioning of index-organized tables |
dbms_lob operations to non-Oracle targets | Replication of LOB operations generated by dbms_lob are not supported when replicating to non-Oracle targets. |
Other | Replication of rows in which data exceeds 319 KB in size, excluding LOB and LONG columns |
The following table shows whether specific SharePlex features are supported for 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 |
This section contains information about SharePlex support for capture from a SQL Server source database and replication to supported targets.
SharePlex support for SQL Server as a target for Oracle data is documented in System Requirements — Oracle.
SharePlex supports Capture for SQL Server versions 2012, 2014, and 2016 on Windows 2012 R2.
Source |
Target - Platform/Database |
---|---|
Windows 2012 R2 on-premise |
Windows 2012 R2 on-premise |
SQL Server 2012 |
SQL Server 2012 |
SQL Server 2014 |
SQL Server 2014 |
SQL Server 2016 |
SQL Server 2016 |
|
Oracle 11.2 |
|
Oracle 12.1 |
|
Linux RHEL 5.5 on-premise |
|
Oracle 11.2 |
|
Linux RHEL 6.3 on-premise |
|
Oracle 12.1 |
|
Solaris SPARC 11 on-premise |
|
Oracle 11.2 |
|
Azure Windows 2012 R2 (IaaS) |
|
SQL Server 2012 |
|
SQL Server 2014 |
|
SQL Server 2016 |
|
Azure SQL Database (PaaS) |
|
SQL Server 2012 |
|
SQL Server 2014 |
|
AWS Linux EC2 (IaaS) |
|
SQL Server |
|
Oracle |
|
AWS Linux RDS (PaaS) |
|
SQL Server |
|
Oracle |
This section shows the limitations of capturing from a SQL Server source.
SharePlex supports INSERT, UPDATE, and DELETE operations between SQL Server source tables and Oracle or SQL Server target tables.
Any SQL Server table can be replicated to an Oracle or SQL Server target if the target supports all of the column types that are being replicated.
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.
SharePlex does not support the replication of SQL Server DDL operations.
SharePlex supports DML operations that contain the following SQL Server data types:
Note: When replicating to an Oracle target, SharePlex queries the target database to determine the appropriate data type to use.
The following table shows whether or not SharePlex features are supported when SQL Server is the source.
SharePlex feature | Supported with SQL Server Target | Supported with Oracle Target |
---|---|---|
Replication between tables in same database | No | No |
Replication between tables in different databases in the same or another SQL Server instance | Yes | Yes |
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 | No | Yes |
Conflict resolution | No | Yes |
Peer-to-peer replication (bi-directional) | No | No |
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) | No | Yes |
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 | No | Yes |
Review and satisfy all of the requirements in this checklist before installing SharePlex or before your SharePlex consultant arrives, if you have contracted with our Professional Services team.
Note: The requirements in this checklist apply to all source and target systems where SharePlex will be installed unless otherwise noted.
Requirement | Completed? (Y/N) |
---|---|
Add SharePlex users and groups to the nameserver. If you are installing SharePlex in a network managed by a nameserver such as NIS or NISPLUS, do the following before you install SharePlex:
The SharePlex security groups spadmin (administrator), spopr (operator), and spview (viewer) control access to SharePlex processes. Add each SharePlex user to one of these groups on the nameserver. For more information, see Assign SharePlex users to security groups. To add the user groups:
To add SharePlex groups to the local system after you install SharePlex, see Assign SharePlex users to security groups. |
|
Ensure that SharePlex can resolve host names. If you find that SharePlex cannot connect to a host, try mapping the host name to an alphanumeric alias in the following locations:
In these files, put each entry on an individual line. The following is an example, where sysA and sysB are aliases: 111.22.33.44 sysA.company.com sysA # source system 55.66.77.88 sysB.company.com sysB # target system |
|
Resolve to the right network card If you have multiple network cards on Windows, you must set the SP_SYS_HOST_NAME environment variable to the network card name or IP address that you want SharePlex to use as the local host. Otherwise, if the server reboots after the SharePlex configuration is activated, the IP address may bind to a different network card from the one that is bound in the replication configuration. For more information about SharePlex environment parameters and how to set them, see the SharePlex Reference Guide. |
|
(PostgreSQL) Add a source entry to the PostgreSQL pg_hba.conf file For a PostgreSQL target (non-cloud), make certain that the PostgreSQL pg_hba.conf file has an entry for the SharePlex source server IP address, which gives that server access to PostgreSQL target server and its databases. Example entry: host all all sourceip md5 |
|
(Oracle) Allow access to Amazon EC2 instance For an EC2 instance, make certain that the appropriate network group is set up to allow access to EC2 instances. |
|
Verify the SharePlex port number. By default SharePlex uses the port number 2100 (hex equivalent is 834) for both TCP/IP and UDP. If port 2100 is available to SharePlex, no further action is needed. You will need to enter the SharePlex port number during the installation procedure, at which time you can specify a different port number if needed. Important! The SharePlex port number must be the same one on all machines in the replication configuration so that they can communicate through TCP/IP connections. Make certain the SharePlex port number is open for both TCP/IP and UDP on the firewall. |
|
Verify TCP/IP settings SharePlex replicates over any TCP/IP network connection. Typically, if all of the tables in a database are being replicated, SharePlex replicates about 33 percent of the redo log volume, the remainder being mostly maintenance data used by the Oracle software. The following is a formula for determining bandwidth. (size of a redo log) x (number of log switches in 1 hour) x 1/3 = volume of data per hour For example, if the redo logs are 20 MB in size, and they switch six times an hour, SharePlex will replicate approximately 40 MB each hour: 20 x 6 x 1/3 = 40 MB/hour |
|
VerifyTCP protocol SharePlex has been tested on IP v6 networks, but it is impossible to test all scenarios. See the System Requirements in the SharePlex Release Notes for more informationon. |
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy