Using Tdsbind Syntax - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ied1556235912841.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1100
lifecycle
previous
Product Category
Teradata Vantage™

Run tdsbind from the Teradata Vantage command prompt. Enter the tdsbind options needed for your test, for example:

su - teradata
tdsbind [-u  dir_user  | -U  td_user] –option  value  -option  value...
The following rules apply when using tdsbind:
  • Become the teradata user (su - teradata) if the system is configured for CA certificates as part of setting up SSL/TLS. This causes tdsbind to run under the Linux user teradata instead of root, which accurately represents how the system processes authentication when CA certificates are present. Also see SSL/TLS Protection Options.
  • You can specify tdsbind options in any order, but they must be separated by spaces.
  • The input is case sensitive, for example, the meaning of -u is completely different than -U.
  • Options that have a corresponding LDAP mechanism property, for example -B (LdapBaseFQDN) are deprecated, although still usable. Where possible, use -O to specify the corresponding LDAP property values in a space-separated list instead of using the individual deprecated options.
    If you simultaneously specify an LDAP property value in the -O option, for example LdapBaseFQDN, and also specify the corresponding standalone option (-B), tdsbind fails.