1. Oracle GoldenGate Classic Architecture Documentation
  2. Prepare
  3. Prepare Your Database for Oracle GoldenGate Classic Architecture
  4. Sybase
  5. Understanding What's Supported for Sybase
  6. Supported Sybase Data Types
  7. Integers

Integers

  • BIGINT

  • BIT

  • DECIMAL

  • INT (signed and unsigned)

  • TINYINT (signed and unsigned)

  • NUMERIC

  • SMALLINT (signed and unsigned)

Limitations of Support

  • NUMERIC and DECIMAL (fixed-point) are supported with no integrity loss when moving data to a target column of the same data type without involving calculations or transformation. When calculations or transformation must be performed, Oracle GoldenGate supports a maximum value of a signed long integer (32-bits).

  • BIT is supported for automatic mapping between Sybase databases. To move BIT data between Sybase and another database type, Oracle GoldenGate treats BIT data as binary. In this case, the following are required:

    • The BIT column must be mapped to the corresponding source or target column with a COLMAP clause in a TABLE or MAP statement.

  • For the Sybase 157 GA release, these data types cannot be replicated:

    • BIGINT (as a key column)

    • BIGDATETIME

    • BIGTIME

  • When replicating TINYINT and Extract is not in the same version of Replicat, you will need to create a sourcedef and/or targetdef file even if you are replicating between identical Sybase versions.

  • See also Non-Supported Sybase Data Types.