Documentation
Advanced Search


Installing and Configuring Oracle GoldenGate for Teradata

1 System Requirements and Preinstallation Instructions

This chapter contains the requirements for the system and database resources that support Oracle GoldenGate. It contains the following sections:

1.1 Overview of Oracle GoldenGate for Teradata

Oracle GoldenGate supports the replication of data as follows:

  • between a Teradata source database (known as a source server) and a Teradata target database (known as a subscriber server).

  • between Teradata databases and other supported database platforms.

In addition, Oracle GoldenGate replicates DDL operations between identical Teradata source and subscriber servers.

Oracle GoldenGate receives transactional changes or table-copy operations from the Teradata Change Data Capture (CDC) facility and transmits them to the subscriber over ODBC. Communication between the CDC and Oracle GoldenGate is managed by the Teradata Access Module (TAM).

Oracle GoldenGate for Teradata supports the filtering, mapping, and transformation of data unless noted otherwise in this documentation.

1.2 What this Documentation Provides

This documentation contains information that is specific to the setup of the Oracle GoldenGate solution within a Teradata environment. It assumes that the reader has a fundamental knowledge of the Teradata database and the Teradata Replication Solutions. It also assumes that the following have been configured properly:

  • Relay Services Gateway (RSG)

  • Change Data Capture (CDC)

  • Teradata Access Module (TAM)

  • Replication groups

To configure replication for the Teradata database, see the Teradata Replication Solutions documentation from Teradata Corporation.

1.3 Supported Platforms for a Replication Server

In a Teradata environment, you install Oracle GoldenGate on a server that is separate from the one where the Teradata source and target databases are installed. This machine will be the replication server and must be a platform that is supported by Oracle GoldenGate for the Teradata database. To find out which Oracle GoldenGate builds are available for a specific combination of database version and operating system, log onto http://support.oracle.com and select the Certifications tab. For assistance, click Tips for Finding Certifications. An e-mail and password are required to enter this site.

Some notes about choosing a replication server or servers:

  • The replication server can exist in the same location as the source or target server, or it can be remote from one or both. For replication between Teradata systems in remote locations, install the Oracle GoldenGate Extract process on a replication server at the source location, and install the Oracle GoldenGate Replicat process on a different replication server at the target location.

  • If possible, install Oracle GoldenGate on a multi-node cluster server to minimize the impact of any Oracle GoldenGate outages that are caused by server failure.

For additional configuration considerations, consult the Teradata Replication Services Using Oracle GoldenGate documentation from Teradata Corporation before installing Oracle GoldenGate.

1.4 Operating System Requirements

This section outlines the operating system resources that are necessary to support Oracle GoldenGate. These resources may apply to the database servers, the replication server(s), or all servers.

1.4.1 Memory Requirements

The amount of memory that is required for Oracle GoldenGate depends on the amount of data being processed, the number of Oracle GoldenGate processes running, the amount of RAM available to Oracle GoldenGate, and the amount of disk space that is available to Oracle GoldenGate for storing pages of RAM temporarily on disk when the operating system needs to free up RAM (typically when a low watermark is reached). This temporary storage of RAM to disk is commonly known as swapping or paging (herein referred to as swapping). Depending on the platform, the term swap space can be a swap partition, a swap file, a page file (Windows) or a shared memory segment (IBM i platforms).

Modern servers have sufficient RAM combined with sufficient swap space and memory management systems to run Oracle GoldenGate. However, increasing the amount of RAM available to Oracle GoldenGate may significantly improve its performance, as well as that of the system in general.

Typical Oracle GoldenGate installations provide RAM in multiples of gigabytes to prevent excessive swapping of RAM pages to disk. The more contention there is for RAM the more swap space that is used.

Excessive swapping to disk causes performance issues for the Extract process in particular, because it must store data from each open transaction until a commit record is received. If Oracle GoldenGate runs on the same system as the database, the amount of RAM that is available becomes critical to the performance of both.

RAM and swap usage are controlled by the operating system, not the Oracle GoldenGate processes. The Oracle GoldenGate cache manager takes advantage of the memory management functions of the operating system to ensure that the Oracle GoldenGate processes work in a sustained and efficient manner. In most cases, users need not change the default Oracle GoldenGate memory management configuration.

For more information about evaluating Oracle GoldenGate memory requirements, see the CACHEMGR parameter in Reference for Oracle GoldenGate for Windows and UNIX.

1.4.2 Disk Requirements

The recommended hardware configuration for the Oracle GoldenGate replication server is:

  • Four 300-GB disks

  • 4 dual-core CPUs

  • 8 GB of RAM

Assign the following free disk space:

  • To determine the size of the Oracle GoldenGate download file, view the Size column before downloading your selected build from Oracle Software Delivery Cloud. The value shown is the size of the files in compressed form. The size of the expanded Oracle GoldenGate installation directory will be significantly larger on disk. For more information, see Section 2.2, "Downloading Oracle GoldenGate."

  • Allow at least an additional 1 GB of disk space on any system that hosts Oracle GoldenGate trails, which are files that contain the working data. You may need more or less than this amount, because the space that is consumed by the trails depends on the volume of data that will be processed. See the guidelines for sizing trails in Administering Oracle GoldenGate for Windows and UNIX.

  • To install Oracle GoldenGate into a cluster environment, install the Oracle GoldenGate binaries and files on a shared file system that is available to all cluster nodes.

1.4.3 Relay Services Gateway (RSG) vprocs

Replication tasks run on RSG vprocs on the source database server for connections with the replication server. The connection implements the TCP/IP protocol. As of Teradata V12, each system node can have one RSG.

1.4.4 Network

The following network resources must be available to support Oracle GoldenGate.

  • Configure the systems that are involved with Oracle GoldenGate to use TCP/IP services, including DNS. Oracle GoldenGate supports IPv4 and IPv6 and can operate in a system that supports one or both of these protocols.

  • Configure the network with the host names or IP addresses of all systems that will be hosting Oracle GoldenGate processes and to which Oracle GoldenGate will be connecting. Host names are easier to use.

  • Oracle GoldenGate requires some unreserved and unrestricted TCP/IP ports, the number of which depends on the number and types of processes in your configuration. See Administering Oracle GoldenGate for Windows and UNIX for details on how to configure the Manager process to handle the required ports.

  • Keep a record of the ports that you assigned to Oracle GoldenGate. You will specify them with parameters when configuring the Manager process.

  • Configure your firewalls to accept connections through the Oracle GoldenGate ports.

1.4.5 Operating System Privileges

The Manager process requires an operating system user that has privileges to control Oracle GoldenGate processes and to read, write, and purge files and subdirectories in the Oracle GoldenGate directory. The Extract and Replicat processes require privileges to access the database.

1.4.6 Console

The operating system and the command console must have the same character sets. Mismatches occur on Microsoft Windows systems, where the operating system is set to one character set, but the DOS command prompt uses a different, older DOS character set. Oracle GoldenGate uses the character set of the operating system to send information to GGSCI command output; therefore a non-matching console character set causes characters not to display correctly. You can set the character set of the console before opening a GGSCI session by using the following DOS command:

chcp OS character set

If the characters do not display correctly after setting the code page, try changing the console font to Lucida Console, which has an extended character set.

1.4.7 Other Programs

The following are additional considerations in support of Oracle GoldenGate.

  • Before installing Oracle GoldenGate on a Windows system, install and configure the Microsoft Visual C ++ 2010 SP1 Redistributable Package. Make certain it is the SP1 version of this package, and make certain to get the correct bit version for your server. This package installs runtime components of Visual C++ Libraries. For more information, and to download this package, go to http://www.microsoft.com.

  • Oracle GoldenGate fully supports virtual machine environments created with any virtualization software on any platform. When installing Oracle GoldenGate into a virtual machine environment, select a build that matches the database and the operating system of the virtual machine, not the host system.

1.5 Database Requirements

This section contains Oracle GoldenGate requirements that are specific to the Teradata database.

1.5.1 Database Configuration

Follow these requirements for database configuration:

  • Install an appropriate ODBC (Open Database Connectivity) driver for the database version that you are using. Oracle GoldenGate supports database versions 13.10, 14.00 and 14.10.x.

  • Configure ODBC on each source and target system, including the creation of a data source name (DSN). A DSN stores information about how to connect to the database. See the ODBC Driver for Teradata User Guide at http://www.info.teradata.com/ for instructions.

  • Create Teradata replication groups for the source tables. For instructions, see the Teradata Replication Services Using Oracle GoldenGate documentation, at http://www.info.teradata.com.

1.5.2 Database User for Oracle GoldenGate Processes

Follow these requirements for the database user for Oracle GoldenGate processes:

  • Create a database user that is dedicated to Oracle GoldenGate. It can be the same user for all of the Oracle GoldenGate processes that must connect to a database:

    • Extract (source database)

    • Replicat (target database)

    • The DEFGEN utility (source or target database)

  • To preserve the security of your data, and to monitor Oracle GoldenGate processing accurately, do not permit other users, applications, or processes to log on as, or operate as, the Oracle GoldenGate database user.

  • If using Oracle GoldenGate to capture from a source Teradata database, issue the following security grants to the Extract database user.

    GRANT SELECT ON DBC.REPGROUP TO user;
    
    GRANT SELECT ON DBC.TVM TO user;
    
    GRANT SELECT ON DBC.DBASE TO user;
    
    GRANT SELECT ON DBC.ERRORMSGS TO user;
    
    GRANT SELECT ON DBC.TVFIELDS TO user;
    
    GRANT SELECT ON DBC.INDEXES TO user;
    
    GRANT SELECT ON DBC.INDOUBTRESLOG TO user;
    
    GRANT REPLCONTROL TO user;
    
    GRANT ALL ON database TO user;
    
    GRANT ALL ON SYSUDTLIB TO user WITH GRANT OPTION;
    
  • If using Oracle GoldenGate to replicate to a target Teradata database, grant SELECT, INSERT, UPDATE, and DELETE on all of the target tables to the Replicat database user.

1.6 Supported Teradata Data Types

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

Table 1-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


1.6.1 Limitations of Support for Numeric Data Types

Numeric data types are fully supported between Teradata source and target databases. 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.

1.6.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 a Teradata source and Teradata targets, and 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.

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

  • Source Teradata tables can contain only CHAR, VARCHAR, INTEGER, SMALLINT, DATE, TIME, and TIMESTAMP columns. No other data types can be replicated while multi-byte data is being replicated.

  • 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 and the Teradata Access Module (TAM) 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.

  • To support Unicode on Linux, Oracle GoldenGate must be configured in pass-through mode, and the ODBC Teradata Linux driver must be version 12.0.0.7 or higher, or 13.0.0.5 or higher. For more information about pass-through mode, see the PASSTHRU parameter in Reference for Oracle GoldenGate for Windows and UNIX.

1.6.4 Limitations of Support for Binary Data Types

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

1.6.5 Limitations of Support for Large Object Data Types

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

  • To replicate UDTs, the target database must be Teradata Database 12.00.00.01 or greater or later.

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

1.6.6 Limitations of Support for Date Data Types

The following are limitations of support for date data types:

  • Date types are fully supported between Teradata source and Teradata target databases. Additionally, INTERVAL is supported between Teradata and Oracle if the size of the target column is equal to, or greater than, that of the source.

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

1.6.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. To include IDENTITY in a bi-directional replication configuration, the ranges of the values defined on the source and target systems must be disjoint, for example odd on one and even on the other.

1.7 Supported Objects and Operations for Teradata

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

1.7.1 DML

Oracle GoldenGate supports the maximum number of columns per table that is supported by the database.

1.7.2 DDL

A Teradata DDL statement can be replicated when it satisfies one of the following conditions:

  • The DDL statement affects a table that is a member of a replication group.

  • The DDL statement matches a user-defined replication rule.

  • The DDL statement changes certain properties of a replication group.

Table 1-2 shows the Teradata DDL operations that Oracle GoldenGate supports. Statement lengths of up to 2 MB in length are supported. At least TAM 13.0 is required, and both source and target databases must be Teradata Database 13.0 or later.

Table 1-2 Supported Teradata DDL

Operations Object

CREATE

TABLE table nameFoot 1 

GLOBAL TEMPORARY TABLE table nameFoot 2 

[RECURSIVE] VIEW view name

MACRO macro name

HASH INDEX index name

JOIN INDEX index name

TRIGGER trigger name

ALTER

TABLE

DROP

TABLE table name

VIEW view name

MACRO macro name

HASH INDEX index name

JOIN INDEX index name

TRIGGER trigger name

RENAME

TABLE table name TO

VIEW view name TO

MACRO macro name

TRIGGER trigger name

GRANT ... ON

REVOKE ... ON

TABLE table name

VIEW view name

MACRO macro name

REPLACE

[RECURSIVE] VIEW view name

TRIGGER trigger name

MACRO macro name

COMMENT ONFoot 3 

TABLE table name

COLUMN table name.column name

VIEW view name

COLUMN view name.column name

MACRO macro name

TRIGGER trigger name

COLLECT STATISTICS ONFoot 4 

DROP STATISTICS ON

table name


Footnote 1 DDL operations on tables that are members of a replication group are automatically captured.

Footnote 2 DDL statements that refer to the temporary materialized state of the table cannot be replicated.

Footnote 3 Only COMMENT statements that create a user-defined description of an object in the data dictionary are captured.

Footnote 4 Only the optimizer form that is used by the Optimizer for generating table access and join plans is captured.

Note:

The actual size limit of the DDL support is approximate, because the size will not only include the statement text but also Oracle GoldenGate maintenance overhead that depends on the length of the object name, the DDL type, and other characteristics of keeping a DDL record internally.

The following DDL statements that change the properties of replication groups will be replicated automatically.

  • ALTER REPLICATION GROUP with ADD and/or DROP clauses

  • CREATE REPLICATION RULESET

  • REPLACE REPLICATION RULESET

  • DROP REPLICATION RULESET

Note:

An ALTER REPLICATION GROUP statement that is used to generate a new security token will not be replicated.

For additional support limitations and configuration instructions, see Chapter 5, "Configuring DDL Synchronization for a Teradata Database."

Close Window

Table of Contents

Installing and Configuring Oracle GoldenGate for Teradata

Expand | Collapse