逻辑备库和goldengate不支持的数据类型

Non-Supported Oracle Data Types

逻辑备库：

https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/data-type-ddl-support-on-logical-standby-databases.html#GUID-76E70ADB-0709-4403-BA6A-379CEAFE758A

C.1 Datatype Considerations
See these topics for information about supported and unsupported database objects.

Supported Datatypes in a Logical Standby Database

Unsupported Datatypes in a Logical Standby Database

C.1.1 Supported Datatypes in a Logical Standby Database
These are the datatypes that logical standby databases support.

Logical standby databases support the following datatypes:

Abstract Data Types (ADTs) and ADT tables

ADTs cannot contain any data types that are not supported as a top-level column type (for example, nested tables, PKREFs, BFILE, unsupported opaque types).

For a table with ADT columns to be supported there must be a primary key (or at least a unique constraint or unique index) that consists solely of scalar top-level columns (scalar ADT attributes cannot be part of such a candidate key).

BINARY_DOUBLE

BINARY_FLOAT

BLOB, CLOB, and NCLOB stored as BasicFile and SecureFiles. SecureFiles can be compressed, encrypted, or deduplicated. SecureFiles support requires that the primary database be running at a compatibility of 11.2 or higher. See Support for SecureFiles LOBs

CHAR

DATE

INTERVAL YEAR TO MONTH

INTERVAL DAY TO SECOND

LONG

LONG RAW

NCHAR

NUMBER

NVARCHAR2

Objects stored as VARRAYs (except for Collections)

Oracle Text

RAW

Multimedia (See exceptions listed in Unsupported Datatypes in a Logical Standby Database.):

ORDAudio

ORDDataSource (internal)

ORDDicom

ORDDoc

ORDImage

ORDSource (internal)

ORDVideo

Spatial (See exceptions listed in Unsupported Datatypes in a Logical Standby Database.)

TIMESTAMP

TIMESTAMP WITH TIMEZONE

TIMESTAMP WITH LOCAL TIMEZONE

VARCHAR and VARCHAR2

XMLType data for all storage models, assuming the following primary database compatibility requirements:

XMLType stored in CLOB format requires that the primary database be run at a compatibility setting of 11.0 or higher (XMLType stored as CLOB is deprecated as of Oracle Database 12c Release 1 (12.1).)

XMLType stored in object-relational format or as binary XML requires that the primary database be running Oracle Database 11g Release 2 (11.2.0.3) or higher with a redo compatibility setting of 11.2.0.3 or higher

Note:SQL Apply does not support statements that have function calls that perform DML on ADT, LOB, or XMLType columns.
Note:As of Oracle Database 12c Release 1 (12.1), the maximum size of the VARCHAR2, NVARCHAR2, and RAW datatypes has been increased to 32 KB when the COMPATIBLE initialization parameter is set to 12.0 or later and the MAX_STRING_SIZE initialization parameter is set to EXTENDED. Logical standby databases support this increased size in most cases. See "Ensure Table Rows in the Primary Database Can Be Uniquely Identified" for known restrictions.
C.1.1.1 Compatibility Requirements
SQL Apply support for theses features has compatibility requirements on the primary database:

Multibyte CLOB support requires primary database to run at a compatibility of 10.1 or higher.

IOT support without LOBs and Overflows requires primary database to run at a compatibility of 10.1 or higher.

IOT support with LOB and Overflow requires primary database to run at a compatibility of 10.2 or higher.

TDE support requires primary database to run at a compatibility of 11.1 or higher.

Basic compression and advanced row compression require the primary database to run at a compatibility of 11.1 or higher.

Hybrid Columnar Compression support is dependent on the underlying storage system.

See Also:

Oracle Database Concepts for more information about Hybrid Columnar Compression

C.1.1.2 Opaque Type Restrictions
These are the restrictions regarding opaque types.

SYS.ANYDATA is supported as long as the instance does not store user-defined opaque data types or BFILEs.

SYS.ANYDATASET, SYS.ANYTYPE, and user-defined opaque types are not supported.

C.1.2 Unsupported Datatypes in a Logical Standby Database
Some data types are not supported by logical standby databases.

If a table contains columns having any of the following unsupported data types, then the entire table is ignored by SQL Apply. (See Support for Data Types That Lack Native Redo-Based Support for information about support for data types that lack native redo-based support.)

ROWID, UROWID

Note that only logical UROWID columns are supported. Non-logical UROWID are detected at run-time, the DML is skipped, and a trace message is written to the report file.

Nested tables

Objects with nested tables

Identity columns

C.2 Support for Data Types That Lack Native Redo-Based Support
The Extended Datatype Support (EDS) feature provides a mechanism for logical standbys to support certain data types that lack native redo-based support.

Note:As of Oracle Database 18c, Extended Datatype Support (EDS) is deprecated. All EDS-supported Oracle data types are now supported natively by logical standbys or Oracle GoldenGate.
For example, tables with SDO_GEOMETRY columns can be replicated using EDS. (Source tables must have a primary key.)

You can query the DBA_LOGSTDBY_EDS_SUPPORTED view to find out which tables are candidates for EDS.

goldengate:

https://docs.oracle.com/en/middleware/goldengate/core/21.3/coredoc/prepare-oracle-understanding-whats-supported.html#GUID-DAFB9FF6-7514-4B54-A32C-B4BE2E721485

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



Non-supported Objects and Operations in Oracle DML
The following are additional Oracle objects or operations that are not supported by Extract:

REF  are supported natively for compatibility with Oracle Database 12.2 and higher, but not primary-key based REFs (PKREFs)

Sequence values in an active-active bi-directional configuration

Database Replay

Tables created as EXTERNAL