LOGON | Usage Notes | Teradata FastLoad - 17.10 - Usage Notes - FastLoad

Teradata® FastLoad Reference

Product
FastLoad
Release Number
17.10
Published
June 2021
Last Update
2021-07-01
Content Type
Programming Reference
Publication ID
B035-2411-061K
Language
English (United States)

The following table describes the things to consider when using the LOGON command.

Usage Notes for LOGON 
Topic Usage Notes
Logon Parameters For standard logon, the parameters (tdpid, username, password, and acctid) are used in all sessions established with the database. The LOGON command may occur only once.

For single sign-on logon, if the Gateway to the database is configured to use single sign-on (SSO), and the user is already logged on to the Teradata client machine, the machine name, user name, and password are not required in the LOGON command. The user name and password combination specified when the user logged on to the Teradata client machine are authenticated via network security for a single sign-on such that valid Teradata users will be permitted to log on to the database. The use of SSO is strictly optional, unless the Gateway has been configured to accept only SSO-style logons.

To connect to a database system other than the one currently logged on, the TDPid must be included in the LOGON command. If the TDPid is not specified, the default contained in clispb.dat will be used. See the Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems, B035-2418 for information about setting defaults.

To be interpreted correctly, the TDPid must be followed by the slash separator (‘/’) to distinguish the TDPid from a database username. For example, to connect to slugger, enter one of the following:

.LOGON slugger/;

.LOGON slugger/,,'acctinfo';

If an account ID is to be used, the optional account ID must be specified in the LOGON command.

To prevent the password from appearing in the script, use Teradata Wallet. See Teradata Vantage™ - Advanced SQL Engine Security Administration, B035-1100 and the appropriate Teradata Tools and Utilities installation guide for more information.
Starting Teradata FastLoad The LOGON command starts a Teradata FastLoad job and automatically establishes:
  • Two Teradata SQL sessions
  • A number of Teradata FastLoad sessions
  • When Teradata FastLoad attempts to connect the Main SQL session the first time and the database is down, Teradata FastLoad displays an error message and terminates.
  • When Teradata FastLoad attempts to connect the Main SQL session but not the first time, or the Auxiliary SQL session, or the data sessions and the database is down. Teradata FastLoad retries to connect 16 times; if the database is still down, Teradata FastLoad displays an error message and terminates.
Number of Sessions The number of Teradata FastLoad sessions depends on the system limitations described in the "Session Limits" section of Restrictions and Limitations.
Teradata FastLoad attempts to connect sessions, in groups of 16, until either:
  • The number of sessions specified with a SESSIONS command are connected
  • Database Error 2632 is returned
  • Some other session limit is reached
If the number that was specified in a SESSIONS command exceeds the number of available sessions, Teradata FastLoad logs only the number of available sessions.
Reported Sessions After a LOGON command is entered, Teradata FastLoad reports the number of Teradata FastLoad sessions that are logged on. The Teradata SQL sessions are not included in this report.
Character Support Current multi-byte character support of an object name is limited to 30 bytes for the database that does not support EON and limited to 128 characters for the database that supports EON.

The limitation applies to username, passwd, and account in the logon string.

CLIv2 treats logon strings of UTF-8 and other Teradata-supported multi-byte character sets (Chinese, Japanese, Korean) as ASCII. CLI does not convert before parsing, so some logon strings with multi-byte characters (or a combination of multi-byte characters plus ASCII) could fail if the total size of an object name is over 30 bytes for the database that does not support EON and is over 128 characters for the database that supports EON.

The work around is to create object names that are less than 30 bytes for the database that does not support EON are less than 128 characters for the database that supports EON.