This chapter contains the requirements for the system and database resources that support Oracle GoldenGate. It contains the following sections:
Section 1.2, "Verifying Certification and System Requirements"
Section 1.7, "Supported Objects and Operations for Teradata"
Oracle GoldenGate release 12c (12.2.0.1) and later only for Teradata supports the delivery of data from other types of databases to a Teradata database.
High-speed Oracle GoldenGate replication can be used to refresh a Teradata cache environment with minimal latency. In addition, with its heterogeneous support, Oracle GoldenGate enables the Teradata data store to be used as a data integration point for other data sources.
Oracle GoldenGate for Teradata supports the filtering, mapping, and transformation of data unless noted otherwise in this documentation.
Make sure that you are installing your product on a supported hardware or software configuration. For more information, see the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.
Oracle has tested and verified the performance of your product on all certified systems and environments; whenever new certifications occur, they are added to the proper certification document right away. New certifications can occur at any time, and for this reason the certification documents are kept outside of the documentation libraries and are available on Oracle Technology Network.
In a Teradata environment, you install Oracle GoldenGate on a server that is separate from the one where the Teradata 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.
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.
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.
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).
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.
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.
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, "Understanding and Obtaining the Oracle GoldenGate Distribution."
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.
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.
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 Replicat processes require privileges to access the database.
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.
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">>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.
This section contains Oracle GoldenGate requirements that are specific to the Teradata database.
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.x through 14.10.00.06.
Configure ODBC on each 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.
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:
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.
For 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.
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 |
|---|---|---|---|
|
|
No |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
No |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
No |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
No |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
Yes |
Yes |
Yes |
|
|
No |
Yes |
Yes |
|
|
No |
Yes |
Yes |
|
|
No |
Yes |
Yes |
|
|
No |
Yes |
Yes |
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.
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.
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.
No limitations. These data types are supported between other source databases and Teradata targets.
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.
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.
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.
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.
This section lists the data operations that Oracle GoldenGate does not support.
Extract (capture)
DDL