31 Understanding What's Supported for Oracle TimesTen

This chapter contains information on database and table features supported by Oracle GoldenGate.

Topics:

Supported Objects and Operations for TimesTen

The following objects and operations are supported:

  • Oracle GoldenGate for Oracle TimesTen supports delivery of transactional DML to user tables.

  • INSERT, UPDATE, DELETE, and TRUNCATE operations are supported.

Non-Supported TimesTen Data Types and Features

The INTERVAL and ROWID data types are not supported.

Supported TimesTen Data Types

The following data types are supported for delivery, unless specifically noted in the limitations that follow:

  • Binary Data Types

    (binary, varbinary)
  • Character Data Types

    (char, nchar, nvarchar2, varchar2)
  • Date and Time Data Types

    (date, time, timestamp, tt_date, tt_time, tt_timestamp)
  • Numeric Data Types

    (binary_float, binary_double, double, float, tt_bigint, tt_integer, number, real, tt_smallint, tt_tinyint)
  • LOB

    (blob, clob, nclob)

Limitations and Non-supported Items for Oracle TimesTen

The limitations and non-supported items for Oracle TimesTen are:

  • Capture (extraction) of DML operations is not supported.

  • Capture and replication of DDL (data definition language) operations is not supported.

  • 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.

  • 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.

  • Modifying the Primary Key Column value is not supported.

  • Limitations on Automatic Heartbeat Table support are as follows:

    • Oracle GoldenGate supports only Delivery on TimesTen so no mechanism is required to populate/update the heartbeat tables using any event/job schedulers.

    • 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 TimesTen 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.