23 Understanding What's Supported for Teradata

This chapter contains support information for Oracle GoldenGate on Teradata databases.

Topics:

Parent topic: Using Oracle GoldenGate with Teradata

23.1 Supported Teradata Data Types

Table 23-1 shows the Teradata data types that Oracle GoldenGate supports. Any limitations or conditions that apply follow this table.

Table 23-1 Supported Data Types by Oracle GoldenGate, Per Teradata Version

Data type v12 v13 v13.1

BLOB

No

Yes

Yes

BYTEINT

Yes

Yes

Yes

VARBYTE

Yes

Yes

Yes

BIGINT

Yes

Yes

Yes

BYTEINT

Yes

Yes

Yes

DATE

Yes

Yes

Yes

DECIMAL - 18 and under

Yes

Yes

Yes

DECIMAL - 19 to 38

No

Yes

Yes

DOUBLE PRECISION

Yes

Yes

Yes

FLOAT

Yes

Yes

Yes

INTEGER

Yes

Yes

Yes

NUMERIC - 18 and under

Yes

Yes

Yes

NUMERIC - 19 to 38

No

Yes

Yes

REAL

Yes

Yes

Yes

SMALLIINT

Yes

Yes

Yes

TIME

Yes

Yes

Yes

TIMESTAMP

Yes

Yes

Yes

INTERVAL

Yes

Yes

Yes

INTERVAL DAY

Yes

Yes

Yes

INTERVAL DAY TO HOUR

Yes

Yes

Yes

INTERVAL DAY TO MINUTE

Yes

Yes

Yes

INTERVAL DAY TO SECOND

Yes

Yes

Yes

INTERVAL HOUR

Yes

Yes

Yes

INTERVAL HOUR TO MINUTE

Yes

Yes

Yes

INTERVAL HOUR TO SECOND

Yes

Yes

Yes

INTERVAL MINUTE

Yes

Yes

Yes

INTERVAL MINUTE TO SECOND

Yes

Yes

Yes

INTERVAL MONTH

Yes

Yes

Yes

INTERVAL SECOND

Yes

Yes

Yes

INTERVAL YEAR

Yes

Yes

Yes

INTERVAL YEAR TO MONTH

Yes

Yes

Yes

CHAR

Yes

Yes

Yes

CLOB

No

Yes

Yes

CHAR VARYING

Yes

Yes

Yes

LONG VARCHAR

Yes

Yes

Yes

VARCHAR

Yes

Yes

Yes

GRAPHIC

Yes

Yes

Yes

LONG VARGRAPHIC

Yes

Yes

Yes

VARGRAPHIC

Yes

Yes

Yes

PERIOD (DATE)

No

Yes

Yes

PERIOD (TIME)

No

Yes

Yes

PERIOD (TIMESTAMP)

No

Yes

Yes

UDT

No

Yes

Yes

Parent topic: Understanding What's Supported for Teradata

23.1.1 Limitations of Support for Numeric Data Types

When replicating these data types from a different type of database to Teradata, truncation can occur if the source database supports a higher precision that 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.

Parent topic: Supported Teradata Data Types

23.1.2 Limitations of Support for Single-byte Character Data Types

Single-byte character types are fully supported within a single-byte Latin character set between other databases and Teradata. A VARCHAR or CHAR column cannot have more than 32k-1 bytes. If using UTF-16, this is 16k-2 characters.

Parent topic: Supported Teradata Data Types

23.1.3 Conditions and Limitations of Support for Multi-byte Character Data

Conditions and limitations of support for multi-byte character data are as follows:

  • Install Oracle GoldenGate on a Windows or Linux replication server.

  • Use the Teradata ODBC driver version 12.0.0.x or later.

  • Do not use filtering, mapping, and transformation for multi-byte data types.

  • A CHAR or VARCHAR column cannot contain more than 32k-1 bytes. If using UTF-16, these columns cannot contain more than 16k-2 characters.

  • Set the ODBC driver to the UTF-16 character set in the initialization file.

  • When creating Replicat groups, use the NODBCHECKPOINT option with the ADD REPLICAT command. The Replicat database checkpointing 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.

Parent topic: Supported Teradata Data Types

23.1.4 Limitations of Support for Binary Data Types

No limitations. These data types are supported between other source databases and Teradata targets.

Parent topic: Supported Teradata Data Types

23.1.5 Limitations of Support for Large Object Data Types

The following are limitations of support for large object data types.

  • To replicate large objects from other databases to Teradata, use Teradata ODBC driver version 12.0 or higher on the target system. The target must support large objects that are delivered by ODBC.

  • Enable the UseNativeLOBSupport flag in the ODBC configuration file. See the Teradata ODBC documentation.

Parent topic: Supported Teradata Data Types

23.1.6 Limitations of Support for Date Data Types

The following are limitations of support for date data types:

  • DATE, TIME, and TIMESTAMP are fully supported when replicated from a different type of source database to Teradata.

  • TIME with TIMESZONE, TIMESTAMP with TIMEZONE, and INTERVAL 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 timezone, conversion may add or subtract hours, which can cause the timestamp to exceed the lower or upper supported limit.

  • Oracle GoldenGate does not support negative dates.

Parent topic: Supported Teradata Data Types

23.1.7 Limitations of Support for IDENTITY Data Types

IDENTITY must be configured as GENERATED BY DEFAULT AS IDENTITY on the target to enable the correct value to be inserted by Replicat.

Parent topic: Supported Teradata Data Types

23.2 Supported Objects and Operations for Teradata

This section lists the data operations and database objects that Oracle GoldenGate supports.

  • 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 with Oracle GoldenGate 12.2.x and greater.

  • Limitations on Automatic Heartbeat Table support are as follows:

    • Teradata does not have any internal event/job schedulers so automatic updating and inserting of records into Heartbeat tables cannot occur.

    • The ALTER HEARTBEATTABLE command is not supported and if used is ignored.

    • The ADD HEARTBEATTABLE command with the FREQUENCY, PURGE_FREQUENCY, or RETENTION_TIME option is not supported. When any of these options are specified with the ADD 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 tables cannot occur. As such, you should explicitly drop or truncate the corresponding heartbeat objects to suit your environment.

Parent topic: Understanding What's Supported for Teradata

23.3 Non-Supported Operations for Teradata

This section lists the data operations that Oracle GoldenGate does not support.

  • Extract (capture)

  • DDL

Parent topic: Understanding What's Supported for Teradata