Teradata SQL Error and Failure Codes from Error 08071 to 08084

SQLServerF1

08071 Deprecated logons are not allowed. Upgrade client software to latest version.
Explanation: The gateway detected a deprecated logon sequence and deprecated logons are not allowed. Upgrade the
client application to a version which supports encrypted passwords.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Correct the configuration. If the problem persists, contact the National Support Center.

08072 %s
Explanation: This error message is used to display tdgss status information.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Correct the configuration. If the problem persists, contact the National Support Center.

08073 Logon Authentication Failed
Explanation: This error message is used to display the results of the tdgss_accept_sec_context call which is used to
authenticate users. The most probable reason for this error is the user specified an invalid set of credentials. Other possible
reasons include incorrect tdgss configuration information or network infrastucture problems.
Generated By: Gateway
For Whom: System Administrator
Remedy: Verify the user is specifying the correct set of credentials for the mechansim the user is specifying. Verify the
tdgss configuration information is correct. If the problem persists, contact the National Support Center.

08074 Logon Timed Out
Explanation: The connection was closed as the client exceeded the connection timeout during the logon sequence.
Generated By: Gateway
For Whom: System Administrator
Remedy: Verify if the user is genuine with the IP address/Port specified. If the frequency of the message is abnormally
high, contact the Global Support Center.

08078 A non-fatal error was returned by the security library call: %s
Explanation: The security library returned an error which was could not be isolated to a single session. Therefore, the
gateway could not continue.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Correct the configuration. If the problem persists, contact the National Support Center.

08079 A fatal error was returned by the security library call: %s
Explanation: The security library returned an error which was could not be isolated to a single session. Therefore, the
gateway could not continue.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Correct the configuration. If the problem persists, contact the National Support Center.

08080 Secure Sign-on Only allowed and unable to initialize
Explanation: Secure Sign-on only specified and unable to load the secure library.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Correct the configuration. If the problem persists, contact the National Support Center.

08081 External Authentication only required and unable to initialize Security Library. Unable to continue
Explanation: The gateway was unable to load the secure library. Since only external authentication is allowed, the gateway
cannot provide a connection to the database.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Correct the configuration. If the problem persists, contact the National Support Center.

08082 Invalid Configuration Warning: %s
Explanation: Either the gateway configuration, the PE configuration, the Lan configuration, the host group or the service
setup is invalid, or they are inconsistent. If the problem can be resolved by the gateway rebuilding its GDO, as is the
case when the inconsistency is caused by a configuration change since the last time the gateway started, the message will
note that the gateway is rebuilding its GDO, and the gateway should come up normally. If the problem cannot be resolved
by rebuilding the GDO, a default value will be used that should allow the gateway to come up normally, unless the value
had been changed from its default. Note that a configuration change that prompts a gateway GDO rebuild can be intentional,
as when host group membership is rearranged, or unintentional, as when a hardware problem forces a node to drop
out, and again when the node rejoins after the problem is resolved.
Generated By: Gateway
For Whom: Field Engineer
Remedy: If the gateway cannot resolve the problem itself, you should correct the configuration. If the problem persists,
contact the National Support Center.

08083 Gateway not started in Gateway Vproc: %s
Explanation: The Gateway was not started in a vproc defined as type gateway.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Correct the configuration. If problem persist, contact the Global Support Center.

08084 Gateway Thread failed to start: %s
Explanation: One of the required gateway threads failed to start.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 08071 to 08084  received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *