15.10 - Teradata ODBC Driver Advanced Options - ODBC Driver for Teradata

ODBC Driver for Teradata User Guide

Product
ODBC Driver for Teradata
Release Number
15.10
Content Type
User Guide
Publication ID
B035-2509-035K
Language
English (United States)

Click the Advanced button in the Warning area of the Teradata ODBC Driver Options dialog box to see further options available. The Teradata ODBC Driver Advanced Options dialog box appears.

Advanced Options Caution

Note: It is strongly recommended NOT to change the settings in the Teradata ODBC Driver Advanced Options dialog box.

 

Table 13: Teradata ODBC Driver Advanced Options 

Field, Check Box, or Button

Description

Application Catalog Database

Default = Blank

Use this option for applications (such as PowerBuilder) that require a database for their system catalog tables.

Enter a database name in the text box.

Using this feature is not recommended, because it is deprecated. For details, see Appendix E: “Deprecated Features”the ODBC Driver for Teradata User Guide.

See the “AppCatalogDB=<database name>” option in Table 23 on page 66.

Maximum Response Buffer Size

Default = 65536 (64K)

Enter the value used to try to limit the Teradata response buffer size for SQL requests. This value can be adjusted dynamically if Teradata cannot send a result within the limited packet size defined.

See the “MaxRespSize=<integer 1048576>” option in Table 23 on page 66.

Redisplay Reconnect Wait

This feature has been deprecated for ODBC Driver for Teradata 14.10.

For more information, see the ODBC Driver for Teradata User Guide.For more information, see “Redisplay Reconnect Wait DSN Option” on page 166.

TDMST Port Number

Default = 1025

Lists the port number to use to access Teradata Database. Do not change this value unless instructed to do so by Technical Support.

See the “TDMSTPortNumber=<integer>” option in Table 23 on page 66.

State Check Level

Default = 0

Provides enhanced ODBC state checking that detects SQLState 24000 according to the requirements in the ODBC SDK. This is a user‑defined option.

Using this feature is not recommended, because it is deprecated. For details, see Appendix E: “Deprecated Features”the ODBC Driver for Teradata User Guide.

See the “StCheckLevel=[0 | 1 | 2]” option in Table 23 on page 66.

Translation DLL Name

Specifies the translation DLL path. Translation DLL is used to convert between session character set and application character set.

See “Session Character Sets and Translation DLLs” on page 52.

Translation Option

Specifies the translation DLL option. The option is used by translation DLL.

See “Session Character Sets and Translation DLLs” on page 52.

Login Timeout

Default = 20

Defines a value corresponding to the number of seconds to wait when establishing a virtual circuit with Teradata for login. Enter an integer value.

See Table 23 on page 66.

ProcedureWithPrintStmt

Default = N

Activates the print option when creating stored procedures.

See the “PrintOption=[N | P]” option in Table 23 on page 66.

ProcedureWithSPLSource

Default = Y

Specifies the SPL option when creating stored procedures.

See the “SplOption=[Y | N]” option in Table 23 on page 66.

Data Source DNS Entries

The Data Source DNS Entries DSN option notifies the ODBC Driver for Teradata how many entries are defined in DNS for the database name. The initial value of this option controls how the ODBC Driver for Teradata resolves database names to IP addresses. If this value is not set, the default value is undefined (empty). If multiple database names are provided in ODBC DSN, the Data Source DNS Entries option is applicable to all names.

Note: If a database is identified by IP address instead of a name in the ODBC DSN or connection-string, the Data Source DNS Entries option is ignored. The database is identified in the Name(s) or IP address(es) field described in “Table 11: ODBC Driver Setup” on page 37ODBC Driver Setup.

Data Source DNS Entries=undefined (default setting) is recommended for best results. This setting enables the ODBC Driver for Teradata to lookup DNS dynamically and find all available COPs for a given database name. Using this approach, ODBC Driver for Teradata will automatically detect new nodes added to the Teradata database (and DNS) in the future, without ODBC modification. For more information, see “Resolving a Data Source Name” on page 51Resolving a Data Source Name.

Data Source DNS Entries = 0 indicates that DNS does not contain cop entries for the database name. The database name will only be resolved by itself. No attempt will be made to resolve using a cop suffix. This behavior can be desirable in an environment utilizing DNS to load balance. When DNS is used for load balancing, administrators can configure DNS to provide a different IP address or multiple IP addresses in different order each time the database name is resolved using DNS.

Data Source DNS Entries = value. Entering a non-zero value indicates that DNS contains cop entries for the database name and the last cop entry is value. The first connection attempt will chose a random number between 1 and value. Each subsequent connection will then increment to the next number (round-robin). This approach will not encounter costly DNS resolution failures (how costly depends on how the DNS is configured). However, if additional entries are added to DNS at a later time, they will not be discovered by the ODBC Driver for Teradata unless the supplied value is increased.

Enable DSN Tracing

Apple OS X only.

The Enable DSN Tracing option controls whether DSN tracing is enabled or disabled.

  • Unchecked (default) = disabled
  • Checked = enabled
  • Path: Specifies the absolute path of the trace file.

    The default is /tmp/ODBC.Trace.xxxxx. If the entry is missing, a default pathname of /tmp/ODBC.Trace.xxxxx is used, where xxxxx is the pid of the creating process.

    Disable PREPARE

    Default = Cleared

    Enables ODBC Driver for Teradata to bypass asking Teradata to perform Prepare before executing a request.

    See the “DisablePREPARE=[Yes | No]” option in Table 23 on page 66.

    Using this feature is not recommended, because it is deprecated. For details, see Appendix E: “Deprecated Features.”

    Use TCP_NODELAY

    Default = Selected

    Valid for the Teradata DSN in ODBC Driver for Teradata.

    Transmission Control Protocol (TCP) provides an option called TCP_NODELAY to control the transmission of data.

    See the “TCPNoDelay=[Yes | No]” option in Table 23 on page 66.

    Use NULL for Catalog Name

    Default = Cleared

    When this option is selected – NULL values are assumed for the Catalog Name parameters in any of the Catalog API functions, even if the application passes a value.

    When this option is cleared and a value is passed for the Catalog Name parameter instead of NULL – ODBC Driver for Teradata returns an error because catalogs are not supported by Teradata Database.

    Disable Prepare for SQL with comments or parenthesis

    Default = Cleared

    Allows Prepare to be executed for SQL request statements enclosed in parentheses or preceded by comments.

    See the “SQLWithCommentsOrParenthesis=[Yes | No]” option in Table 23 on page 66.

    Using this feature is not recommended, because it is deprecated. For details, see Appendix E: “Deprecated Features”

    Enable Read Ahead

    Default = Selected

    When this option is selected - the ODBC Driver reads ahead by requesting the next response message from the database when the current response message being processed is not the last. The database can have one request active for each session at any point in time. An active request is either an SQL request which is executing or a request for the next part of the result from an earlier SQL request.

    When this option is cleared - the ODBC Driver only requests the next response message from the database when the current response message has been processed by the driver.

    Retry system calls (EINTR)

    Default = Selected

    When this option is selected – the ODBC Driver is responsible for retrying the socket system calls when they have been interrupted by some event such as a SIGALRM.

    When this option is cleared – the ODBC Driver returns an SQL_ERROR to the ODBC Application. The ODBC Application is responsible for recovery from the interrupted socket system calls.

    Custom options group box

    Use DATE data for TIMESTAMP parameters

    Default = Cleared

    When this option is selected– ODBC Driver for Teradata is directed to send DATE data for parameters bound as SQL_C_TIMESTAMP and SQL_TIMESTAMP.

    This option should not be enabled for applications that are not using Microsoft Access Jet databases.

    This option should only be selected for this circumstance, as this results in truncation of SQL_C_TIMESTAMP data to contain only the DATE portion.

    Enable Custom Catalog Mode for 2.x Applications

    Default = Cleared

    Provides backwards compatibility for ODBC 2.x applications that have taken advantage of a defect in the ODBC Driver where the functionality of the Catalog APIs are noncompliant with the ODBC Programmers Reference specification.

    The behavior when a NULL value is passed to the SQLTables API for the SchemaName argument results in a search for tables belonging to the userid, DBC, and default database schema names, rather than a % search pattern as noted in the ODBC Programmers Reference Specification.

    Return Empty string in CREATE_PARAMS column for SQL_TIMESTAMP

    Default = Cleared

    Returns an empty string for the CREATE_PARAMS column of SQLGetTypeInfo for SQL_TIMESTAMP data type, and disallows MC-ACCESS from using any TIMESTAMP precision value in Create Table text.

    Return max. CHAR/VARCHAR length as 32K

    Default = Cleared

    Returns a value of 32000 (in general, could be 64000 also) for COLUMN_SIZE column of SQLGetTypeInfo for SQL_CHAR and SQL_VARCHAR data types. This allows MS-ACCESS to handle column size value returned by ODBC Driver for Teradata without any numeric overflow.

    Upon completion, return to each previous screen in the sequence by clicking the OK button.

    After entering the required information into the ODBC Driver Setup for Teradata Database dialog box, click the OK button.

    The data source that you just configured displays in the user Data Sources list of the ODBC Data Source Administrator dialog box.

    To continue adding data sources, repeat the process.

  • ODBC Driver Setup Parameters
  • Teradata ODBC Driver Options
  • Resolving a Data Source Name