Known Issues for Oracle

Running ExpressConnect for Oracle with Replication Server.

ExpressConnect 15.5 for Oracle requires Replication Server 15.5 ESD #1, while ExpressConnect 15.5 ESD #1 for Oracle requires Replication Server 15.6.

Workaround: Use the correct version of ExpressConnect for Oracle with your Replication Server installation.

Oracle XML table fails to replicate.

Replication Server cannot replicate the data manipulation language (DML) statements issued against an Oracle XMLType table.

Workaround: None.

ExpressConnect for Oracle does not support opaque datatypes.

The Replication Server opaque datatype is not supported by ExpressConnect for Oracle 15.5, which means that this version of ExpressConnect for Oracle cannot support user-defined datatypes and the Oracle anydata function.

Workaround: None.

ExpressConnect for Oracle fails when bulk copy is enabled and the bulk copy threshold is set to 1.

ExpressConnect for Oracle fails when you set dsi_bulk_copy to on and dsi_bulk_threshold to 1. Setting dsi_bulk_threshold to 1 deteriorates and suspends the Data Server Interface (DSI).

Workaround: Set dsi_bulk_threshold to 2 or higher.

DirectConnect fails with an error message when replicating XML.

ECDA does not support replication of XML data. When replicating a table with XML data, ECDA displays an error message stating that a column in the table does not exist.

Workaround: Migrate to ExpressConnect for Oracle.

No support for automatic failover when replicating into a RAC system.

ECDA 15.0 and earlier supports replication into an Oracle instance, even if the instance is a node in a Real Application Cluster (RAC) system. However, if the configured node fails, ECDA 15.0 and earlier does not support automatically failing over to another node in the RAC system.

Workaround: When the node that the ECDA service is connected to fails, reconfigure the ECDA service to use a different node in the RAC system.

LOB value not being applied to existing row.

When replicating a LOB column, ECDA for Oracle first determines the ROWID value for the Oracle row that should contain the LOB. The row for that ROWID is updated with the LOB value. However, if the table in the replicate Oracle database is a reference table, and the parent table is partitioned across multiple tablespaces, then the ROWID returned for the reference table may be incorrect, resulting in the LOB value not being applied to the expected row. The Oracle bug ID for this incorrect ROWID problem is 8417690.

Workaround: None.