These limitations apply to Extract.

• Oracle GoldenGate supports tables that contain any number of rows.

• A row can be up to 4 MB in length. If Oracle GoldenGate is configured to include both the before and after image of a column in its processing scope, the 4 MB maximum length applies to the total length of the full before image plus the length of the after image. For example, if there are UPDATE operations on columns that are being used as a row identifier, the before and after images are processed and cannot exceed 4 MB in total. Before and after images are also required for columns that are not row identifiers but are used as comparison columns in conflict detection and resolution (CDR). Character columns that allow for more than 4 KB of data, such as a CLOB, only have the first 4 KB of data stored in-row and contribute to the 4MB maximum row length. Binary columns that allow for more than 4kb of data, such as a BLOB the first 8 KB of data is stored in-row and contributes to the 4MB maximum row length.

• Oracle GoldenGate supports the maximum number of columns per table that is supported by the database.

• Oracle GoldenGate supports the maximum column size that is supported by the database.

• Oracle GoldenGate supports tables that contain only one column, except when the column contains one of the following data types:

  • LOB

  • LONG

  • LONG VARCHAR

  • Nested table

  • User Defined Type (UDT)

  • VARRAY

  • XMLType

• Set DBOPTIONS ALLOWUNUSEDCOLUMN before you replicate from and to tables with unused columns.

• Oracle GoldenGate supports tables with these partitioning attributes:

  • Range partitioning

  • Hash Partitioning Interval Partitioning

  • Composite Partitioning

  • Virtual Column-Based Partitioning

  • Reference Partitioning

  • List Partitioning

• Oracle GoldenGate supports tables with virtual columns, but does not capture change data for these columns or apply change data to them: The database does not write virtual columns to the transaction log, and the Oracle Database does not permit DML on virtual columns. For the same reason, initial load data cannot be applied to a virtual column. You can map the data from virtual columns to non-virtual target columns.

• Oracle GoldenGate will not consider unique/index with virtual columns.

• Oracle GoldenGate supports replication to and from Oracle Exadata. To support Exadata Hybrid Columnar Compression, the source database compatibility must be set to 11.2.0.0.0 or higher.

• Oracle GoldenGate supports Transparent Data Encryption (TDE).

• Oracle GoldenGate supports TRUNCATE statements as part of its DDL replication support, or as standalone functionality that is independent of the DDL support.

• Oracle GoldenGate supports the capture of direct-load INSERT, with the exception of SQL*Loader direct-path insert for XML Binary and XML Object Relational. Supplemental logging must be enabled, and the database must be in archive log mode. The following direct-load methods are supported.

  • /*+ APPEND */ hint

  • /*+ PARALLEL */ hint

  • SQLLDR with DIRECT=TRUE

• Oracle GoldenGate fully supports capture from compressed objects for Extract.

• Oracle GoldenGate supports XA and PDML distributed transactions.

• Oracle GoldenGate supports DML operations on tables with FLASHBACK ARCHIVE enabled. However, Oracle GoldenGate does not support DDL that creates tables with the FLASHBACK ARCHIVE clause or DDL that creates, alters, or deletes the flashback data archive itself.

These limitations apply to Extract.

• Oracle GoldenGate supports capture from a view when Extract is in initial-load mode (capturing directly from the source view, not the redo log).

• Oracle GoldenGate does not capture change data from a view, but it supports capture from the underlying tables of a view.

Materialized views are supported by Extract with the following limitations.

• Materialized views created WITH ROWID are not supported.

• The materialized view log can be created WITH ROWID.

• The source table must have a primary key.

• Truncates of materialized views are not supported. You can use a DELETE FROM statement.

• DML (but not DDL) from a full refresh of a materialized view is supported. If DDL support for this feature is required, open an Oracle GoldenGate support case.

• For Replicat the Create MV command must include the FOR UPDATE clause

• Either materialized views can be replicated or the underlying base table(s), but not both.

These limitations apply to Extract.

• Oracle GoldenGate does not support the replication of sequence values in an active-active bi-directional configuration.

• The cache size and the increment interval of the source and target sequences must be identical. The cache can be any size, including 0 (NOCACHE).

• The sequence can be set to cycle or not cycle, but the source and target databases must be set the same way.

• Tables with default sequence columns are excluded from replication for Extract.