Teradata: Supported Data Types, Objects, and Operations
This section contains information on supported data types, objects, and operations for Oracle GoldenGate on Teradata.
Supported Teradata Data Types
BLOB
BYTE
VARBYTE
BIGINT
BYTEINT
DATE
DECIMAL
DOUBLE PRECISION
FLOAT
INTEGER
NUMBER
NUMERIC
REAL
SMALLIINT
TIME
TIMESTAMP
INTERVAL
INTERVAL DAY
INTERVAL DAY TO HOUR
INTERVAL DAY TO MINUTE
INTERVAL DAY TO SECOND
INTERVAL HOUR
INTERVAL HOUR TO MINUTE
INTERVAL HOUR TO SECOND
INTERVAL MINUTE
INTERVAL MINUTE TO SECOND
INTERVAL MONTH
INTERVAL SECOND
INTERVAL YEAR
INTERVAL YEAR TO MONTH
CHAR
CLOB
CHAR VARYING
LONG VARCHAR
VARCHAR
GRAPHIC
LONG VARGRAPHIC
VARGRAPHIC
Limitations of Support for Data Types
Here are the details of conditions and limitations of support for data types.
Date Data Types
-
TIME with TIMESZONE
,TIMESTAMP with TIMEZONE
, andINTERVAL
are not supported from a different type of source database to Teradata. -
Oracle GoldenGate supports timestamp data from 0001/01/03:00:00:00 to 9999/12/31:23:59:59. If a timestamp is converted from GMT to local time, these limits also apply to the resulting timestamp. Depending on the time zone, conversion may add or subtract hours, which can cause the timestamp to exceed the lower or upper supported limit.
IDENTITY
Columns
IDENTITY
must be configured as GENERATED BY DEFAULT AS
IDENTITY
on the target to enable the correct value to be inserted by
Replicat.
Large Object Data Types
The following is the limitation of support for large object data types:
-
Enable the
UseNativeLOBSupport
flag in the ODBC configuration file. See the Teradata ODBC documentation.
Numeric Data Types
When replicating the numeric data types to Teradata, truncation can occur if the source database supports a higher precision than Teradata does.
The support of range and precision for floating-point numbers depends on the host machine. In general, the precision is accurate to 16 significant digits, but you should review the database documentation to determine the expected approximations. Oracle GoldenGate rounds or truncates values that exceed the supported precision.
Multi-byte Character Data
-
Filtering, mapping, and transformation for multi-byte data types is not supported.
-
Set the ODBC driver to the UTF-16 character set in the initialization file.
-
When creating a Replicat, use the
NODBCHECKPOINT
option with theADD REPLICAT
command. The Replicat database check-pointing feature does not support an ODBC driver that is set to the UTF-16 character set. Checkpoints will be maintained in the checkpoint file on disk.
Supported Objects and Operations for Teradata
This section lists the data operations and database objects that Oracle GoldenGate supports.
-
Oracle GoldenGate for Teradata supports delivery (Replicat) of DML transactions to Teradata.
-
Oracle GoldenGate supports the maximum number of columns per table that is supported by the database.
-
Truncating operations are supported with the use of the
GETTRUNCATES
parameter. -
Limitations on Automatic Heartbeat Table support are as follows:
-
The
ALTER HEARTBEATTABLE
command is not supported and if used is ignored. -
The
ADD HEARTBEATTABLE
command with theFREQUENCY
,PURGE_FREQUENCY
, orRETENTION_TIME
option is not supported. When any of these options are specified with theADD HEARTBEATTABLE
command, a warning is displayed that the option is ignored. -
Since Teradata does not have any internal event/job schedulers, automatic purging of heartbeat history data does not occur. You need to explicitly delete or truncate records periodically from the heartbeat history table.
-