As of Oracle Database 12c Release 1 (12.1), the maximum size of the VARCHAR2
, NVARCHAR2
, and RAW
data types 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
.
LogMiner treats 32 KB columns as LOBs for the purposes of supplemental logging.
A 32 KB column cannot be part of an ALWAYS supplemental logging group.
LogMiner supports the following data types and table storage attributes. As described in "Compatibility Requirements", some data types are supported only in certain releases.
Data Types
BINARY_DOUBLE
BINARY_FLOAT
BLOB
CHAR
CLOB
and NCLOB
DATE
INTERVAL YEAR TO MONTH
INTERVAL DAY TO SECOND
LOBs stored as SecureFiles (requires that the database be run at a compatibility of 11.2 or higher.
LONG
LONG RAW
NCHAR
NUMBER
NVARCHAR2
Objects stored as VARRAY
s
Objects (Simple and Nested ADTs without Collections)
Object support (including Oracle-supplied types such as SDO_GEOMETRY
, ORDIMAGE
, and so on) requires that the database be running Oracle Database 12c Release 1 (12.1) with a redo compatibility setting of 12.0.0.0 or higher. The contents of the SQL_REDO
column for the XML data-related operations is never valid SQL or PL/SQL.
Oracle Text
RAW
TIMESTAMP
TIMESTAMP WITH TIMEZONE
TIMESTAMP WITH LOCAL TIMEZONE
VARCHAR
and VARCHAR2
XDB
XMLType
data for all storage models, assuming the following primary database compatibility requirements:
XMLType
stored in CLOB
format requires that the 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 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. The contents of the SQL_REDO
column for the XML data-related operations is never valid SQL or PL/SQL.
Table Storage Types
Cluster tables (including index clusters and heap clusters).
Index-organized tables (IOTs) (partitioned and nonpartitioned, including overflow segments).
Heap-organized tables (partitioned and nonpartitioned).
Advanced row compression and basic table compression. Both of these options require a database compatibility setting of 11.1.0 or higher.
Tables containing LOB columns stored as SecureFiles, when database compatibility is set to 11.2 or higher.
Tables using Hybrid Columnar Compression, when database compatibility is set to 11.2.0.2 or higher.
Oracle Database Concepts for more information about Hybrid Columnar Compression