Non-Supported Oracle Data Types

Oracle GoldenGate does not support the following data types.

  • Time offset values outside the range of +12:00 and -12:00..Oracle GoldenGate supports time offset values between +12:00 and -12:00.

  • Tables that only contain a single column and that column one of the following:

    • UDT

    • LOB (CLOB, NCLOB, BLOB, BFILE)

    • XMLType column

    • VARCHAR2 (MAX) where the data is greater than 32KB

  • Tables with LOB, UDT, XML, or XMLType column without one of the following:

    • Primary Key

    • Scalar columns with a unique constraint or unique index

    Table where the combination of all scalar columns do not guarantee uniqueness are unsupported.

  • Tables with the following XML characteristics:

    • Tables with a primary key constraint made up of XML attributes

    • XMLType tables with a primary key based on an object identifier (PKOID).

    • XMLType tables, where the row object identifiers (OID) do not match between source and target

    • XMLType tables created by an empty CTAS statement.

    • XML schema-based XMLType tables and columns where changes are made to the XML schema (XML schemas must be registered on source and target databases with the dbms_xml package).

    • The maximum length for the entire SET value of an update to an XMLType larger than 32K, including the new content plus other operators and XQuery bind values.

    • SQL*Loader direct-path insert for XML-Binary and XML-OR.

  • Tables with following UDT characteristics:

    • UDTs that contain CFILE or OPAQUE (except of XMLType)

    • UDTs with CHAR and VARCHAR attributes that contain binary or unprintable characters

    • UDTs using the RMTTASK parameter

  • UDTs and nested tables with following condition:

    • Nested table UDTs with CHAR, NVARCHAR2 or NCLOB attributes.

    • Nested tables with CLOB, BLOB, extended (32k) VARCHAR2 or RAW attributes in UDTs.

    • Nested table columns/attributes that are part of any other UDT.

  • When data in a nested table is updated, the row that contains the nested table must be updated at the same time. Otherwise there is no support.

  • When VARRAYS and nested tables are fetched, the entire contents of the column are fetched each time, not just the changes. Otherwise there is no support.

  • Object table contains the following attributes:

    • Nested table

    • SDO_TOPO_GEOMETRY

    • SDO_GEORASTER