Teradata

The Teradata connector lets you perform insert, delete, update, and read operations on Teradata database.

Before you begin

Before using the Teradata connector, do the following tasks:

  • In your Google Cloud project:
    • Ensure that network connectivity is set up. For information about network patterns, seeNetwork connectivity.
    • Grant theroles/connectors.admin IAM role to the user configuring the connector.
    • Grant the following IAM roles to the service account that you want to use for the connector:
      • roles/secretmanager.viewer
      • roles/secretmanager.secretAccessor

      A service account is a special type of Google account intended to represent a non-human user that needs to authenticate and be authorized to access data in Google APIs. If you don't have a service account, you must create a service account. The connector and the service account must belong to the same project. For more information, seeCreating a service account.

    • Enable the following services:
      • secretmanager.googleapis.com (Secret Manager API)
      • connectors.googleapis.com (Connectors API)

      To understand how to enable services, seeEnabling services.

    If these services or permissions have not been enabled for your project previously, you are prompted to enable them when configuring the connector.

Teradata configuration

To create a Teradata Vantage Express instance on Google Cloud VM, seeInstall Teradata on Google Cloud VM. If this VM is publicly exposed, then the external IP of this VM can be used as the host address when you create a connection. If the VM isn't publicly exposed, create Private Service Connectivity and use thenetwork endpoint attachment IP when you create a connection.

Configure the connector

A connection is specific to a data source. Itmeans that if you have many data sources, you must create a separate connectionfor each data source. To create a connection, do the following:

  1. In theCloud console, go to theIntegration Connectors > Connections page and then select or create a Google Cloud project.

    Go to the Connections page

  2. Click+ Create new to open theCreate Connection page.
  3. In theLocation section, choose the location for the connection.
    1. Region: Select a location from the drop-down list.

      For the list of all the supported regions, seeLocations.

    2. ClickNext.
  4. In theConnection Details section, complete the following:
    1. Connector: SelectTeradata from the drop down list of available Connectors.
    2. Connector version: Select the Connector version from the drop down list of available versions.
    3. In theConnection Name field, enter a name for the Connection instance.

      Connection names must meet the following criteria:

      • Connection names can use letters, numbers, or hyphens.
      • Letters must be lower-case.
      • Connection names must begin with a letter and end with a letter or number.
      • Connection names cannot exceed 49 characters.
    4. Optionally, enter aDescription for the connection instance.
    5. Optionally, enableCloud logging, and then select a log level. By default, the log level is set toError.
    6. Service Account: Select a service account that has therequired roles.
    7. Optionally, configure theConnection node settings:

      • Minimum number of nodes: Enter the minimum number of connection nodes.
      • Maximum number of nodes: Enter the maximum number of connection nodes.

      A node is a unit (or replica) of a connection that processes transactions. More nodes are required to process more transactions for a connection and conversely, fewer nodes are required to process fewer transactions. To understand how the nodes affect your connector pricing, see Pricing for connection nodes. If you don't enter any values, by default the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.

    8. Note: You can customize the connection node values only if you are a Pay-as-you-go customer.
    9. Database: The database selected as the default database when a Teradata connection is opened.
    10. Charset: Specifies the session character set for encoding and decoding character data transferred to and from the Teradata Database. The default value is ASCII.
    11. Optionally, click+ Add label to add a label to the Connection in the form of a key/value pair.
    12. ClickNext.
  5. In theDestinations section, enter details of the remote host (backend system) you want to connect to.
    1. Destination Type: Select aDestination Type.

      If you want to establish a public connection to your backend systems with additional security, you can considerconfiguring static outbound IP addresses for your connections, and then configure your firewall rules to allowlist only the specific static IP addresses.

      To enter additional destinations, click+Add destination.

    2. ClickNext.
  6. In theAuthentication section, enter the authentication details.
    1. Select anAuthentication type and enter the relevant details.

      The following authentication types are supported by the Teradata connection:

      • Username and password
    2. To understand how to configure these authentication types, seeConfigure authentication.

    3. ClickNext.
  7. Review: Review your connection and authentication details.
  8. ClickCreate.

Configure authentication

Enter the details based on the authentication you want to use.

  • Username and password
    • Username: Username for connector
    • Password: Secret Manager Secret containing the password associated with the connector.

Connection configuration samples

This section provides the sample values for the various fields that you configure when you create a Teradata connector.

Basic authentication - connection type

Field nameDetails
Locationus-central1
Connectorteradata
Connector version1
Connection Nameteradata-vm-connection
Enable Cloud LoggingYes
Service AccountSERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com
DatabaseTERADATA_TESTDB
CharsetASCII
Minimum number of nodes2
Maximum number of nodes2
Destination TypeHost address
host 1203.0.113.255
port 11025
UsernameUSERNAME
PasswordPASSWORD
Secret version1

Entities, operations, and actions

All the Integration Connectors provide a layer of abstraction for the objects ofthe connected application. You can access an application's objects only through this abstraction. The abstraction is exposed to you as entities, operations, and actions.

Note: You can view the entities, operations, and actions of a connector in theConnectors task.
  • Entity:An entity can be thought of as an object, or a collection of properties, in theconnected application or service. The definition of an entity differs from a connector to a connector. For example, in a database connector, tables are the entities, in a file server connector, folders are the entities, and in a messaging system connector, queues are the entities.

    However, it is possible that a connector doesn't support or have any entities, in which case theEntities list will be empty.

  • Operation:An operation is the activity that you can perform on an entity. You can performany of the following operations on an entity:

    Selecting an entity from the available list, generates a list ofoperations available for the entity. For a detailed description of the operations, see the Connectors task'sentity operations. However, if a connector doesn't support any of the entity operations, such unsupported operations aren't listed in theOperations list.

  • Action:An action is a first class function that is made available to the integrationthrough the connector interface. An action lets you make changes to an entity or entities, and vary from connector to connector. Normally, an action will have some input parameters, and an output parameter. However, it is possible that a connector doesn't support any action, in which case theActions list will be empty.
Note:All entities and actions will have a schema associated with them. For example, an action schema will have the parameter details such as; the parameternames, and its corresponding data type. The schema (metadata) for entities and actions is fetched by the connection atruntime from your backend. If there are any updates to the schema, such updates won't be automatically reflected in your existing connections; you must manually refresh the schema. To refreshthe schema for a connection, open theConnection details page of the connection, and then clickRefresh connection schema.

Actions

This connector supports execution of the following actions:

System limitations

The Teradata connector can process a maximum of 70 transactions per second, pernode, andthrottles any transactions beyond this limit. By default, Integration Connectors allocates 2 nodes (for better availability) for a connection.

For information on the limits applicable to Integration Connectors, seeLimits.

Note: The number ofIntegration Connectors nodes will autoscale dynamically based on your usage. However, if you want to reserve capacity for large volumes without waiting for autoscaling, you can adjust the minimum node value for a connection. More nodes are required to process more transactions for a connection. Conversely, fewer nodes are required if a connection processes fewer transactions. To configure the node values, do the following:
  • If you are a pay-as-you-go customer, configure the minimum and maximum node value in the edit connection page.
  • If you are a subscription based customer,contact support.

The maximum transactions that a node can handle depends on various factors. So, before adjusting the minimum nodes for better throughput, it is recommended you check if your backend systems are set up optimally to handle the required traffic.

Supported data types

The following are the supported data types for this connector:

  • BIGINT
  • BINARY
  • BIT
  • BOOLEAN
  • CHAR
  • DATE
  • DECIMAL
  • DOUBLE
  • FLOAT
  • INTEGER
  • LONGN VARCHAR
  • LONG VARCHAR
  • NCHAR
  • NUMERIC
  • NVARCHAR
  • REAL
  • SMALL INT
  • TIME
  • TIMESTAMP
  • TINY INT
  • VARBINARY
  • VARCHAR

Actions

The Oracle DB connector lets you execute your stored procedures, functions, and custom SQL queries in the format supported by your Oracle database. To execute custom SQL queries, the connector provides theExecuteCustomQuery action.

ExecuteCustomQuery action

This action let your execute custom SQL queries.

Input parameters of the ExecuteCustomQuery action

Parameter NameData TypeRequiredDescription
queryStringYesQuery to execute.
queryParametersJSON array in the following format:
[{"value": "VALUE", "dataType": "DATA_TYPE"}]
NoQuery parameters.
maxRowsNumberNoMaximum number of rows to be returned.
timeoutNumberNoNumber of seconds to wait till the query executes.

Output parameters of the ExecuteCustomQuery action

On successful execution, this action returns the status 200 (OK) with a response body that has the query results.

For example on how to configure theExecuteCustomQuery action,seeExamples.

To understand how to useExecuteCustomQuery action, seeAction examples.

Action examples

This section describes how to perform some of the actions in this connector.

Example - Execute a group by query

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query":"select E.EMPLOYEE_ID,E.EMPLOYEE_NAME,E.CITY from EMPLOYEES E LEFT JOIN EMPLOYEE_DEPARTMENT ED ON E.EMPLOYEE_ID=ED.ID where E.EMPLOYEE_NAME = 'John' Group by E.CITY,E.EMPLOYEE_ID,E.EMPLOYEE_NAME"}
  4. This example selects the employee records from theEMPLOYEES and theEMPLOYEE_DEPARTMENT tables. If the action is successful, your connector task'sconnectorOutputPayload response parameter will have the query result set.

Example - Execute a parameterized query

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query":"select C.ID,C.NAME,C.CITY,C.O_DATE,E.EMPLOYEE_ID from customqueries C,Employees E where C.ID=E.Employee_id and C.NAME=?","queryParameters":[{"value":"John","dataType":"VARCHAR"}],"timeout":10,"maxRows":3}
  4. This example selects employee records where the name of the employee isJohn. Notice that the name of the employee is parameterized by using thequeryParameters parameter. If the action is successful, your connector task'sconnectorOutputPayload response parameter will have a value similar to the following:

    [{"NAME":"John","O_DATE":"2023-06-01 00:00:00.0","EMPLOYEE_ID":1.0},{"NAME":"John","O_DATE":"2021-07-01 00:00:00.0","EMPLOYEE_ID":3.0},{"NAME":"John","O_DATE":"2022-09-01 00:00:00.0","EMPLOYEE_ID":4.0}]

Example - Insert a record by using a sequence value

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query":"INSERT INTO AUTHOR(id,title) VALUES(author_table_id_seq.NEXTVAL,'Sample_book_title')"}
  4. This example inserts a record in theAUTHOR table, by using an existingauthor_table_id_seq sequence object. If the action is successful, your connector task'sconnectorOutputPayload response parameter will have a value similar to the following:

    [{}]

Example - Execute a query with an aggregate function

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query":"SELECT SUM(SALARY) as Total FROM EMPLOYEES"}
  4. This example calculates the aggregate value of salaries in theEMPLOYEES table. If the action is successful, your connector task'sconnectorOutputPayload response parameter will have a value similar to the following:

    [{"TOTAL":13000.0}]

Example - Create a new table

  1. In theConfigure connector task dialog, clickActions.
  2. Select theExecuteCustomQuery action, and then clickDone.
  3. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"query":"CREATE TABLE TEST1 (ID INT, NAME VARCHAR(40),DEPT VARCHAR(20),CITY VARCHAR(10))"}
  4. This example creates theTEST1 table. If the action is successful, your connector task'sconnectorOutputPayload response parameter will have a value similar to the following:

    [{}]

Entity operation examples

Example - List all the employees

This example lists all the employees in theEmployee entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectEmployee from theEntity list.
  3. Select theList operation, and then clickDone.
  4. Optionally, inTask Input section of theConnectors task, you can filter your result set by specifying afilter clause.

Example - Get employee details

This example gets the details of the employee with the specified ID, from theEmployee entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectEmployee from theEntity list.
  3. Select theGet operation, and then clickDone.
  4. In theTask Input section of theConnectors task, clickEntityId and then enter45 in theDefault Value field.

    Here,45 is the primary key value of theEmployee entity.

Example - Create a employee record

This example adds a new employee record in theEmployee entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectEmployee from theEntity list.
  3. Select theCreate operation, and then clickDone.
  4. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"EMPLOYEE_ID":69.0,"EMPLOYEE_NAME":"John","CITY":"Bangalore"}

    If the integration is successful, your connector task'sconnectorOutputPayload field will have a value similar to the following:

    {"ROWID":"AAAoU0AABAAAc3hAAF"}

Example - Update an employee record

This example updates the employee record whose ID is 69 in theEmployee entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectEmployee from theEntity list.
  3. Select theUpdate operation, and then clickDone.
  4. In theTask Input section of theConnectors task, clickconnectorInputPayload and then enter a value similar to the following in theDefault Value field:
    {"EMPLOYEE_NAME":"John","CITY":"Mumbai"}
  5. ClickentityId, and then enter69 in theDefault Value field.

    Alternately, instead of specifying theentityId, you can also set thefilterClause to69.

    If the integration is successful, your connector task'sconnectorOutputPayload field will have a value similar to the following:

    {}

Example - Delete an employee record

This example deletes the employee record with the specified ID in theEmployee entity.

  1. In theConfigure connector task dialog, clickEntities.
  2. SelectEmployee from theEntity list.
  3. Select theDelete operation, and then clickDone.
  4. In theTask Input section of theConnectors task, clickentityId and then enter35 in theDefault Value field.

Create connections using Terraform

You can use theTerraformresource to create a new connection.

To learn how to apply or remove a Terraform configuration, seeBasic Terraform commands.

To view a sample terraform template for connection creation, seesample template.

When creating this connection by using Terraform, you must set the following variables in your Terraform configuration file:

Parameter nameData typeRequiredDescription
client_charsetSTRINGTrueSpecifies the Java character set for encoding and decoding character data transferred to and from the Teradata Database.
databaseSTRINGTrueThe database selected as the default database when a Teradata connection is opened.
accountSTRINGFalseSpecifies an account string to override the default account string defined for the Teradata Database user.
charsetSTRINGTrueSpecifies the session character set for encoding and decoding character data transferred to and from the Teradata Database. The default value is ASCII.
column_nameINTEGERTrueControls the behavior of the ResultSetMetaData getColumnName and getColumnLabel methods.
connect_failure_ttlSTRINGFalseThis option enables the CData ADO.NET Provider for Teradata remember the time of the last connection failure for each IP address/port combination. Also, the CData ADO.NET Provider for Teradata skips connection attempts to that IP address/port during subsequent logins for the number of seconds specified by the Connect Failure time-to-live (CONNECTFAILURETTL) value.
connect_functionSTRINGFalseSpecifies whether the Teradata Database should allocate a Logon Sequence Number (LSN) for this session or associate this session with an existing LSN.
copSTRINGFalseSpecifies whether COP Discovery is performed.
cop_lastSTRINGFalseSpecifies how COP Discovery determines the last COP hostname.
ddstatsENUMFalseSpecify the value for DDSTATS. Supported values are: ON, OFF
disable_auto_commit_in_batchBOOLEANTrueSpecifies whether or not disable the autocommit when executing the batch operation.
encrypt_dataENUMFalseSpecify the EncryptData value, ON or OFF. Supported values are: ON, OFF
error_query_countSTRINGFalseSpecifies the maximum number of times that JDBC FastLoad will attempt to query FastLoad Error Table 1 after a JDBC FastLoad operation.
error_query_intervalSTRINGFalseSpecifies the number of milliseconds that JDBC FastLoad will wait in between attempts to query FastLoad Error Table 1 after a JDBC FastLoad operation.
error_table1_suffixSTRINGFalseSpecifies the suffix for the name of FastLoad Error Table 1 created by JDBC FastLoad and JDBC FastLoad CSV.
error_table2_suffixSTRINGFalseSpecifies the suffix for the name of FastLoad Error Table 2 created by JDBC FastLoad and JDBC FastLoad CSV.
error_table_databaseSTRINGFalseSpecifies the database name for the FastLoad error tables created by JDBC FastLoad and JDBC FastLoad CSV.
field_sepSTRINGFalseSpecifies a field separator for use with JDBC FastLoad CSV only. The default separator is ',' (comma).
finalize_auto_closeSTRINGFalseSpecify the value for FinalizeAutoClose, ON or OFF.
geturl_credentialsSTRINGFalseSpecify the value for GeturlCredentials, ON or OFF.
governSTRINGFalseSpecify the value for GOVERN, ON or OFF.
literal_underscoreSTRINGFalseAutomatically escape LIKE-predicate patterns in DatabaseMetaData calls, such as schemPattern and tableNamePattern.
lob_supportSTRINGFalseSpecify the value for LobSupport, ON or OFF.
lob_temp_tableSTRINGFalseSpecifies the name of a table with the following columns: id integer, bval blob, cval clob.
logSTRINGFalseSpecifies the logging level (verbosity) for a connection. Logging is always enabled. The logging levels are listed in order from terse to verbose.
log_dataSTRINGFalseSpecifies additional data needed by a logon mechanism, such as a secure token, Distinguished Name, or a domain/realm name.
log_mechSTRINGFalseSpecifies the Logon Mechanism, which determines the connection's authentication and encryption capabilities.
logon_sequence_numberSTRINGFalseSpecifies an existing Logon Sequence Number (LSN) to associate this session with.
max_message_bodySTRINGFalseSpecifies the maximum Response Message size in bytes.
maybe_nullSTRINGFalseControls the behavior of the ResultSetMetaData.isNullable method.
new_passwordSTRINGFalseThis connection parameter enables an application to change an expired password automatically.
partitionSTRINGFalseSpecifies the Teradata Database partition for the Connection.
prep_supportSTRINGFalseSpecifies whether the Teradata Database performs a prepare operation when a PreparedStatement or CallableStatement is created.
reconnect_countSTRINGFalseEnables Teradata Session Reconnect. Specifies the maximum number of times that the Teradata JDBC Driver will attempt to reconnect the session.
reconnect_intervalSTRINGFalseEnables Teradata Session Reconnect. Specifies the number of seconds that the Teradata JDBC Driver will wait in between attempts to reconnect the session.
redriveSTRINGFalseEnables Teradata Session Reconnect, and also enables automatic redriving of SQL requests interrupted by database restart.
run_startupSTRINGFalseSpecify the value for RunStartup, ON or OFF.
sessionsSTRINGFalseSpecifies the number of FastLoad or FastExport connections to be created, where 1<= number of FastLoad or FastExport connections<= number of AMPs.
sip_supportSTRINGFalseControls whether the Teradata Database and Teradata JDBC Driver use StatementInfo Parcel (SIP) to convey metadata.
slob_receive_thresholdSTRINGFalseControls how small LOB values are received from the Teradata Database. Small LOB values are pre-fetched from the Teradata Database before the application explicitly reads data from Blob/Clob objects.
slob_transmit_thresholdSTRINGFalseControls how small LOB values are transmitted to the Teradata Database.
sp_splSTRINGFalseSpecifies behavior for creating or replacing Teradata stored procedures.
strict_encodeSTRINGFalseSpecifies behavior for encoding character data to transmit to the Teradata Database.
tmodeSTRINGFalseSpecifies the transaction mode for the connection.
tnanoSTRINGFalseSpecifies the fractional seconds precision for all java.sql.Time values bound to a PreparedStatement or CallableStatement and transmitted to the Teradata Database as TIME or TIME WITH TIME ZONE values.
tsnanoSTRINGFalseSpecifies the fractional seconds precision for all java.sql.Timestamp values bound to a PreparedStatement or CallableStatement and transmitted to the Teradata Database as TIMESTAMP or TIMESTAMP WITH TIME ZONE values.
tcpSTRINGFalseSpecifies one or more TCP socket settings, separated by plus signs ().
trusted_sqlSTRINGFalseSpecify the value for TrustedSql.
typeSTRINGFalseSpecifies the type of protocol to be used with the Teradata Database for SQL statements.
upper_case_identifiersBOOLEANFalseThis property reports all identifiers in uppercase. This is the default for Oracle databases and thus allows better integration with Oracle tools such as the Oracle Database Gateway.
use_xviewsSTRINGFalseSpecifies which Data Dictionary views should be queried to return result sets from DatabaseMetaData methods.

Use the Teradata connection in an integration

After you create the connection, it becomes available in bothApigee Integration and Application Integration. You can use the connectionin an integration through the Connectors task.

  • To understand how to create and use the Connectors task in Apigee Integration, seeConnectors task.
  • To understand how to create and use the Connectors task in Application Integration, seeConnectors task.

Get help from the Google Cloud community

You can post your questions and discuss this connector in the Google Cloudcommunity atCloud Forums.

What's next

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.