0xe1000081 The oid string could not be converted to the oid DER format
Explanation: The OID string passed in had an error in it.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
0xe1000082 The mechanism specified in the TDGSS trailer was bad or invalid
Explanation: The first time tdgss_init_sec_context is called for a new context, TDGSS appends a trailer to the output
token. This trailer contained a mechanism type that was invalid.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
0xe1000083 The QOP oid specified in the TDGSS trailer was bad or invalid
Explanation: The first time tdgss_init_sec_context is called for a new context, TDGSS appends a trailer to the output
token. This trailer contained a QOP OID that was invalid.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
0xe1000084 Could not obtain a valid mechanism OID from the TDGSS trailer
Explanation: Without a valid mechanism OID, tdgss_accept_sec_context does not know which mechanism to use.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information
Remedy: Contact the Global Support Center.
0xe1000085 Status value was not a Microsoft status code
Explanation: The code was expecting to have a Microsoft status code. Instead, bit 29 was set, which indicates a customer
status code.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
0xe1000086 Status value was not a UNIX style status code
Explanation: The code was expecting to have a UNIX style status code.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
0xe1000087 tdgss_acquire_cred currently only allows one mechanism to be specified
Explanation: In the GSS spec, gss_acquire_cred allows multiple mechanisms to be specified in an OID set. Currently in
TDGSS, we only allow a single mechanism in the OID set.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
0xe1000088 tdgss_acquire_cred was not able to acquire a credential as requested
Explanation: tdgss_acquire_cred was not able to acquire a credential because a bad security mechanism was passed in.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
0xe1000089 tdgss_init_sec_context was not able to initialize a security context
Explanation: tdgss_init_sec_context was not able to initialize a security context. This can be due to either an invalid
mechanism being selected or no address of a pointer to a security context supplied. The major status will indicate which
reason.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See Major Status code for futher information.
Remedy: Contact the Global Support Center.
0xe100008a tdgss_accept_sec_context was not able to accept a security context
Explanation: tdgss_accept_sec_context requires the address of a pointer to a security context. This was not supplied.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
0xe100008b tdgss_inquire_names_for_mech was not able to obtain name types.
Explanation: tdgss_inquire_names_for_mech requires that a valid mechanism be specified.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
0xe100008c Cannot use the default mechanism for this operation
Explanation: Many TDGSS operations allow the default mechanism to be specified by passing in a NULL point for the
mechanism OID. However, some TDGSS functions do not allow this.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.
Above are list of Teradata Errors or Failure Codes from Error 0xe1000081 To 0xe100008c 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.