Teradata SQL Error and Failure Codes from Error 0xe100008d To 0xe1000098

0xe100008d tdgss_connonicalize_name was not able to return a name as requested
Explanation: tdgss_connonicalize_name requires that a valid mechanism be specified.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe100008e tdgss_indicate_mechs was not able to return a set of mechanisms
Explanation: The caller did not provide any place to write the results.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe100008f tdgss_display_status cannot return status text as requested
Explanation: The status value indicates that the status is from a mechanism, but the mechanism indicated is invalid.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000090 tdgss_configure could not obtain a library path
Explanation: A library path was required but not specified.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000091 tdgss_configure: second parameter (Client/Server) bad
Explanation: The second parameter of tdgss_configure, client_server, was bad.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000092 tdgss_inquire_properties_for_user could not obtain user properties
Explanation: The caller did not provide a place to write the results.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe1000093 The TDGSS Library was not ready
Explanation: The TDGSS Library was probably called before the tdgss_configure completed.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000094 The TDGSS Library was already initialized
Explanation: While tdgss_configure can be called multiple times, the TDGSS library itself is only initialized once.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000095 The TDGSS Library currently has initialization in progress already
Explanation: The TDGSS Library cannot be called until initialization is complete.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000096 There are no valid mechanisms listed in the TDGSS Configuration Files.
Explanation: There must be at least one valid security mechanism for TDGSS to use, otherwise it cannot run.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000097 Multiple default security mechanisms were detected.
Explanation: There cannot be multiple default security mechanisms defined in the TDGSS Configuration Files.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Change the TDGSS Configuration Files to define no more than one default security mechanism.

0xe1000098 The security mechanism selected as default is not a valid mechanism.
Explanation: The default mechanism must be a valid security mechanism.
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 0xe100008d To 0xe1000098 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.

 

Teradata SQL Error and Failure Codes from Error 0xe1000081 To 0xe100008c

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.

 

Teradata SQL Error and Failure Codes from Error 0xe1000076 To 0xe100007f

0xe1000076 The internal buffer that holds this mechanism’s properties is too small.
Explanation: This is an internal TDGSS error.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000077 Could not duplicate buffer as requested
Explanation: The buffer could not be duplicated as requested because either the source or destination buffer (but not
both) was NULL.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe1000078 Could not repackage buffer as requested
Explanation: A valid security mechanism is required to repackage the buffer, but was not supplied.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe1000079 Could not duplicate OidSet as requested
Explanation: The OidSet could not be duplicated because no OidSet destination was specified.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe100007a Could not repackage OidSet as requested
Explanation: A valid security mechanism is required to repackage the OidSet, but was not supplied.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe100007b Could not obtain mechanism oid as requested
Explanation: The mechanism specified could not be found.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe100007c Could not obtain mechanism string as requested
Explanation: The mechanism string could not be obtained. This can be due to either an invalid mechanism being
selected or if there is no place to write the results. The major status will indicate which reason.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe100007d Could not get algorithm QOP as requested
Explanation: The Algorithm QOP could not be obtained. This can be due to either an invalid mechanism being selected
or if there is no place to write the results. The major status will indicate which reason.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe100007e The OID string supplied was too small
Explanation: According to the X.208 specification, an OID string must consist of a minimum of two numbers, separated
by an ASCII “.” This means that the absolute minimum OID string size is 3 (for example “1.2”).
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe100007f Was not able to obtain the DER form of the OID
Explanation: An error has occured in gssp_oidstr_to_oidder.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 0xe1000076 To 0xe100007f 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.

 

Teradata SQL Error and Failure Codes from Error 0xe100006a To 0xe1000075

0xe100006a tdgss_display_name could not generate a display name as requested
Explanation: No name was given for tdgss_display_name to display.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe100006b tdgss_duplicate_name could not duplicate the name as requested
Explanation: An error was encountered while trying to duplicate a name.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe100006c The TDGSS status type passed to tdgss_display_status was invalid
Explanation: The Status Type passed to tdgss_display_status must one of either GSS_C_GSS_CODE or
GSS_C_MECH_CODE. Any other value is invalid.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe100006d The message context pointer passed to tdgss_display_status was NULL
Explanation: TDGSS requires that a non-NULL message context pointer be passed to tdgss_display_status
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe100006e The buffer structure passed to tdgss_display_status was invalid.
Explanation: tdgss_display_status requires a valid buffer structure be passed in by the caller. This error is generally
caused by a NULL pointer being passed in instead.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe100006f The status value passed to tdgss_display_status was invalid or malformed.
Explanation: The status value could not be converted to text by tdgss_display_status because it was invalid or malformed.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000070 The TDGSS OID set was invalid or NULL.
Explanation: An invalid or NULL TDGSS OID set was passed in where a valid OID set is required.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000071 The pointer to the output flag in oid set operations was bad
Explanation: There is no place to return required information from this TDGSS call.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000072 tdgss_inquire_version was given a NULL pointer for the version
Explanation: tdgss_inquire_version requires the user to pass a structure to hold the version. If this doesn’t happen, the
version cannot be returned.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000073 tdgss_inquire_properties_for_mech could not obtain properties as requested
Explanation: tdgss_inquire_properties cannot obtain the properties. Either a NULL pointer was passed in for the buffer
or an invalid mechanism was specified.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000074 tdgss_inquire_one_mech_property could not obtain the property as requested.
Explanation: tdgss_inquire_one_mech_property cannot obtain the property. Either a NULL pointer was passed in for
the buffer or an invalid mechanism was specified.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000075 The mechanism has no properties associated with it
Explanation: Every mechanism must have a number of properties associated with it.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Check the TDGSS Library and User configuration files.

Above are list of Teradata Errors or Failure Codes from Error 0xe100006a To 0xe1000075 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.

 

Teradata SQL Error and Failure Codes from Error 0xe0000006 To 0xe000000f

0xa0000010 The tdgss library is still in memory.
Explanation: The tdgss library has not been unloaded from memory due to additional refrences.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: Check the number of configure and terminate calls.
Remedy: Contact the Global Support Center.

0x20000011 Failed to acquire lock to load TDGSS Library.
Explanation: Failed to acquire lock to load TDGSS Library.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: If the mutex is already locked, the calling thread blocks until the mutex becomes available. This operation returns
with the mutex object in the locked state with the calling thread as its owner. The error is returned when any of the following
occurs: 1. The current thread already owns the mutex. 2. The value specified by mutex does not refer to an initialized
mutex object.
Remedy: N/A

0x20000012 Failed to unlock the acquire lock to load TDGSS Library.
Explanation: Failed to unlock the acquire lock to load TDGSS Library.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: A signal is delivered to a thread waiting for a mutex, upon return from the signal handler the thread resumes
waiting for the mutex as if it was not interrupted. The error is returned when any of the following occurs: 1. The calling
thread does not own the mutex. 2. The mutex has not been properly initialized
Remedy: N/A

0x20000013 The Loadtdgss Library could not allocate a mutex.
Explanation: It appears that the system is running low on resources (possibly memory).
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: The Loadtdgss library needs mutex to protect its global data. This mutex is allocated when the tdgss_configure
function is called. On the UNIX platform (except for MPRAS) pthread mutex is created, on Windows regular mutex is used.
Remedy: N/A

0xe0000014 An invalid version parameter was passed as an argument.
Explanation: The version argument passed in is invalid: it may be in an incorrect format or it may be of invalid length.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: check the parameters passed
Remedy: Contact the Global Support Center.

0x21000064 Successful
Explanation: Successful return from the TDGSS Library
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: N/A

0xe1000065 There is not enough memory to complete this function
Explanation: The function being performed required more memory, but the attempt to allocate more memory failed.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000066 This function is currently not available
Explanation: This function is not available in the TDGSS Library. It may be supported in a future release.
Generated By: TDGSS Package.
For Whom: System Support Representative.

0xe1000067 This function is not available for the requested security mechanism
Explanation: This function is not available for the requested security mechanism because the mechanism has not implemented it.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

0xe1000068 tdgss_release_name could not release the name as requested
Explanation: tdgss_release_name could not release the name structure because it was malformed or corrupted.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

0xe1000069 tdgss_import_name could not import the name as requested
Explanation: tdgss_import_name could not import the name due to a bad parameter on the call.
Generated By: TDGSS Package.
For Whom: System Support Representative.
Notes: See major status for further information.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 0xa0000010 To 0xe1000069 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.

 

Teradata SQL Error and Failure Codes from Error 0xe0000006 To 0xe000000f

0xe0000006 Could not allocate memory needed.
Explanation: the process or system is running low on memory.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: Check log for memory related problem – system is running low on memory.
Remedy: Contact the Global Support Center.

0xe0000007 loadtdgss could not load the tdgss library.
Explanation: The was an error loading the true tdgss library.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: An internal error during the dynamic load of tdgss could have occured.
Remedy: Contact the Global Support Center.

0xe0000008 loadtdgss could not initialize the message trailers.
Explanation: This is an internal error.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: This is an internal error.
Remedy: Contact the Global Support Center.

0xe0000009 The loadtdgss library could not be initialized
Explanation: Another thread was initializing loadtdgss but encountered an error.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: Check the error received by some other thread which made a tdgss_configure call.
Remedy: Contact the Global Support Center.

0xe000000a Could not call loadtdgss function.
Explanation: Loadtdgss was not able to locate the function in the tdgss library
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: MAke a note of the function call made.
Remedy: Contact the Global Support Center.

0xe000000b tdgss_configure called with incorrect parameter.
Explanation: A previous tdgss_configure call was made successfully with different parameters.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: all the tdgss_configure calls need to have the same parameters within the process.
Remedy: Contact the Global Support Center.

0xe000000c number of configure and terminate calls do not match.
Explanation: There appears to be an incorrect match between the configure and terminate calls
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: check the number of tdgss_configure and tdgss_terminate calls made.
Remedy: Contact the Global Support Center.

0xe000000d The user has to specify SERVER or CLIENT in the configure call.
Explanation: the tdgss_configure call should be passed a valid argument
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: check the parameters passed
Remedy: Contact the Global Support Center.

0xe000000e An invalid parameter was passed as an argument.
Explanation: It would appear that a NULL argument was passed
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: check the parameters passed
Remedy: Contact the Global Support Center.

0xe000000f could not locate the tdgss library.
Explanation: loadtdgss could not locate the tdgss directory
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: check the tdgss_configure parameters to see where loadtdgss looked for the tdgss library.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 0xe0000006 To 0xe000000f 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.

 

Teradata SQL Error and Failure Codes from Error 9916 To 0xe0000005

9916 DBQL failed to collect parameter information.
Explanation: DBQL parameterized query logging was requested and the DBC.DBQLParamTbl’s cache size is not big
enough to hold the current request’s data.
Generated By: gncdbqlparam Module.
For Whom: System Administrator.
Remedy: If the user wants to capture parameter information for the specified request, DBSControl performance parameter
DBQLParamCacheSize needs to be adjusted. The new value should be at least the size of failing request’s data.

9922 Diagnostic NOAGGRENH not allowed when the query contains sequenced aggregation.
Explanation: When there is sequenced aggregation in the query, NOAGGRENH diagnostic should be switched off.
Generated By: OPT modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Switch off the NOAGGRENH diagnostic and then resubmit the query.

9930 The SLOB parcel is incorrect.
Explanation: This error occurs if the source SLOB parcel definition is inconsistent. It could be one of the following: a.
The Parameter Order Number in the SLOB Parcel is incorrect. b. The Repr is incorrect, that is not a LOB c. The LOB is not
deferred. d. SLOB parcels are encountered whereas indicator bits indicate NULL.
Generated By: MoveRow.
For Whom: End User.
Notes: This is probably caused by incorrect definition of the input SLOB parcel from the host computer.
Remedy: Check the definition of the input SLOB parcel.

9938 Requested internal memory is more than the allowed maximum limit.
Explanation: The request required too much memory to construct XML And it exceeds the maximum allowable size of
memory in one-shot.
Generated By: DOM modules.
For Whom: End User.
Remedy: Simplify the request and resubmit it,If the request appears to be simple and there is some question as to
whether it should fail for lack of memory, submit the script to your support representative.

9940 SYSTEM VERSIONING cannot be dropped. The table has %VSTR.
Explanation: A temporal table has constraints (CHECK, UNIQUE, PRIMARY KEY or RI) or join index or trigger
defined. The existing constraints or join index or triggers are associated with the temporal time dimension and hence SYSTEM VERSIONING cannot be dropped.
Generated By: OPD modules.
For Whom: End User.
Remedy: Drop the constraints and join indexes and triggers before DROP SYSTEM VERSIONING.

0x20000001 The function call (from the loadtdgss library) was successful.
Explanation: No error occured during the loadtdgss call.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: There was no error
Remedy: Contact the Global Support Center.

0xe0000002 The loadtdgss library is not initialized
Explanation: the tdgss_configure function needs to be called succesfully.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: Unless the loadtdgss library is initialized all subsequent calls will fail.
Remedy: Contact the Global Support Center.

0xe0000003 Another thread is initializining the loadtdgss library.
Explanation: some other thread withing the process is has also made a tdgss_configure() call.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: Try making the tdgss_configure call later.
Remedy: Contact the Global Support Center.

0xe0000004 The number of tdgss functions seem incorrect.
Explanation: This is an internal error which suggests a build problem.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: It may not be possible for the progam to continue.
Remedy: Contact the Global Support Center.

0xe0000005 an invalid pathname was supplied.
Explanation: The user should check the name of the directory passed as an argument.
Generated By: loadtdgss
For Whom: System Support Representative.
Notes: The user specified a path or directory that does not exist.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 9916 To 0xe0000005 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.

 

Teradata SQL Error and Failure Codes from Error 9903 To 9915

9903 The privilege is not applicable to a server.
Explanation: The applicable grant privileges are SELECT, INSERT, SHOW for a server object.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

9904 Specified operation not allowed for server %DBID.%TVMID.
Explanation: DbName or TableName Name value pairs specified as part of server definition should match with the
database name or table name of the query if this is a select or help foreign database statement.
Help foriegn server is not allowed when DbName or TableName name value pair is specified in server definition.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

9905 Privilege cannot be granted as the specified server does not have an associated table operator.
Explanation: The user attempted to Grant Select/Insert privilege on a server object. Error is reported If SELECT privilege
is specified and no import operator is associated with the server object or If INSERT privilege is specified and no
export operator is associated with the server object.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

9906 ’%VSTR’ is not a server.
Explanation: The specified item is a view, macro, permanent journal table, join index, or hash index and the context of
the statement returning the error requires the item to be a normal server.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

9907 Server object not associated with operator.
Explanation: Server object is not associated with the required operator for the statement.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Alter the server object to associate the required operator.

9908 ’%VSTR’ is not allowed when external security is associated with the server.
Explanation: Server object is associated or specified with external security. So ’proxyusername’ or ’proxypass’ NVP not
allowed in a server custom clause.
Generated By: RES Modules.
For Whom: End User.
Remedy: Remove ’proxyusername’ or ’proxypass’ from create or alter server and resubmit the request

9909 ’%VSTR’ is not allowed in a server custom clause.
Explanation: Custom clause for server object must not have names like Columns, Servermode, QualifyColumns,
IsNested, hExplain, Import and Export.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Remove the name specified in error message from custom clause and resubmit.

9911 Invalid use of query %VSTR.
Explanation: The query system time period specification or query TransactionTime period specification or query Valid-
Time period specification must not be given at statement level.
Generated By: RES modules.
For Whom: The end user.
Remedy: Specify the query system time period specification or query TransactionTime period specification or query
ValidTime period specification at Table Level and resubmit.

9912 NORMALIZE is not allowed on a SYSTEM_TIME column.
Explanation: When a table is DDL normalized, then the <Normalize column> must not be system-time column.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9913 Value for system-time column is replaced by a system-generated timestamp.
Explanation: This is only a warning to let the user know that a value specified for a system-time column was replaced
by a system-generated timestamp.
Generated By: Resolver.
For Whom: End User.

9915 A cursor returning a result set to both caller and client is not allowed on select and consume.
Explanation: Teradata does not allow the cursor returning a result set to both caller and client on Select and Consume
statement from a stored procedure.
Generated By: Opt modules.
For Whom: End User.
Remedy: Do not use cursor on Select and Consume, if cursor returns a result set to both caller and client.

Above are list of Teradata Errors or Failure Codes from Error 9903 To 9915 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.

 

Teradata SQL Error and Failure Codes from Error 9891 To 9902

9891 Concurrent load operations are disabled in session.
Explanation: A SET QUERY_BAND command is submitted to set the query band value for LDILoadGroup from a session
that disables load operations.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Enable load operations in the session and re-submit the command.

9892 Specified load isolated operations are disabled on %DBID.%TVMID.
Explanation: A WITH ISOLATED LOADING option is specified in a DML statement and the LDI target table does not
have the DML level enabled for load isolation.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Enable load operations on the table and resubmit the command. Or perform the DML as a nonconcurrent LDI
modification.

9893 Invalid operation on load isolated table.
Explanation: The DMLs within a transaction for a given LDI table must all be nonconcurrent load isolated or all must be
concurrent load isolated DMLs. The specified command violates this rule.
Generated By: Parser modules.
For Whom: End user.
Remedy: Correct the command and resubmit or perform after the on-going operation is completed.

9894 Cannot define a %VSTR for a load isolated table.
Explanation: A load isolated table does not support permanent journals, compressed join index or hash index.
Generated By: Parser modules.
For Whom: End user.
Remedy: Modify the command as applicable to execute successfully. For example, remove the permanent journaling
option. Do not create a compressed join index or hash index on a LDI table.

9895 Cannot define load isolation on a table with permanent journal defined.
Explanation: A load isolated table does not support permanent journals. An alter table command is issued to make a
non-LDI table with permanent journal defined to a LDI table.
Generated By: Parser modules.
For Whom: End user.
Remedy: Remove permanent journaling option to convert the non-LDI table to LDI table Or create a new table without
journaling option from the existing table using CREATE TABLE AS.

9896 Load operation cannot occur as CurrLoadID reached the upper limit.
Explanation: Each concurrent isolated load operation increments the CurrLoadID by 2. The increment is causing the
upper limit of 0x7FFFFFFE to be exceeded and cannot be executed.
Generated By: Parser modules.
For Whom: End user.
Remedy: Perform ALTER TABLE using the RESET LOAD IDENTITY option and then perform the load operation.

9897 MLoad target table may not contain secondary indexes with load identity.
Explanation: MLoad command is issued on a LDI table that defines a NUSI with load identity.
Generated By: Parser modules.
For Whom: End user.
Remedy: Drop the NUS with load identity and resubmit the MLOAD command. Create the index after MLOAD is successful.
Alternatively, see if MLOADX may be used instead that supports all NUSI and USI on LDI tables.

9898 Table %DBID.%TVMID cannot be loaded as the %FSTR table is already in a different load operation.
Explanation: A child and parent LDI tables may not be loaded simultaneously in separate load operations.
Generated By: Parser modules.
For Whom: End user.
Remedy: Either load both the parent and child tables in the same load operation or perform them one after the other.

9900 Duplicate names specified in custom clause.
Explanation: Custom clause for server object must not have duplicate name.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Remove the duplicate name in custom clause and resubmit.

9901 Specified server already exists.
Explanation: The user attempted to create the server. A Server exists with that name. This error occurs on a CREATE
SERVER statement.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Choose a new name for the server and resubmit the request.

9902 Specified ’%VSTR’ option does not exist.
Explanation: The user attempted to alter the server.Specified server attribute option does not exist.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

Above are list of Teradata Errors or Failure Codes from Error 9891 To 9902 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.

 

Teradata SQL Error and Failure Codes from Error 9881 To 9890

9881 Function ’%VSTR’ called with an invalid number or type of parameters
Explanation: The function was either called with an incorrect number of arguments or the data types could not be
implicitly converted to the types accepted by the function. This error can be returned for both embedded functions and
user-defined functions.
Generated By: Parser Modules.
For Whom: End User.
Remedy: If using an embedded function, reference the documentation for details on how to use it. For user-defined functions,
“show function” or “help function” will show the number and type of parameters accepted by the UDF.

9882 An old statistic with same set of columns is replaced with new statistic to honor the new userspecified column ordering during COLLECT STATISTICS processing.
Explanation: An old statistic with same set of columns is replaced with new statistic to honor the new user-specified column
ordering during COLLECT STATISTICS processing.
Generated By: OPT Modules.
For Whom: User.
Remedy: The user should drop the existing multicolumn stats, before collecting stats on same set of columns in a new
order.

9883 Specified table is already a Load Isolated table.
Explanation: An ALTER TABLE command is issued to alter the specified table to be a LDI table. However, the table is
already a load isolated table.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Do not issue the command as it is a load isolated table already.

9884 Cannot add load isolation property for table with %VSTR defined on the table.
Explanation: An ALTER TABLE command is issued to alter the specified table to be a LDI table. The command cannot
be executed successfully if: 1) If the table has NUSI or USI defined 2) If the table has one or more join indexes that are already not marked as load isolated tables. For example a single table join index exists on the table being altered. 3) If the table has column partitions defined on it.
Generated By: Resolver modules.
For Whom: End user.
Remedy: If the table is a column partitioned table, then alter table cannot be used to make the table a LDI table. Otherwise,
drop the index or indexes and re-issue the command.

9885 Cannot drop load isolation property of the table with %VSTR defined on the table.
Explanation: An ALTER TABLE command is issued to alter the specified LDI table to be a non-LDI table. The command
cannot be executed successfully if: 1) If the table has NUSI or USI defined 2) If the table has one or more join indexes that
are already marked as load isolated tables. For example a single table join index exists on the table being altered.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Drop the index or indexes and re-issue the command.

9886 Specified DML level is already set for the Load Isolated table.
Explanation: An ALTER TABLE command is issued on LDI table to alter the DML that must be load isolated. However,
the table already defines the specified DML level to be load isolated
Generated By: Resolver modules.
For Whom: End user.
Remedy: Check the DML level specified and change it to alter. If DML level is the required setting, do not issue the
ALTER table statement.

9887 No load is in progress for the specified load group value.
Explanation: There is no isolated load operation going on using the specified value for the reserved LDILoadGroup
Queryband. This error can occur for any of the following statements: 1) SET QUERY_BAND that specifies the incorrect
query_band value for LDILoadGroup 2) CHECKPOINT ISOLATED LOADING that specifies the incorrect query_band
value for LDILoadGroup. 3) END ISOLATED LOADING that specifies the incorrect query_band value for LDILoadGroup.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Correct the query_band value that corresponds to the required load operation and re-issue the command.

9888 LDILoadGroup cannot be changed while associated load is in progress.
Explanation: The value for the reserved LDILoadGroup is being changed. However, a concurrent isolated load operation
is already in progress and it has not ended.
Generated By: Resolver modules.
For Whom: End user.
Remedy: After the on-going load operation is completed, correct the LDILoadGroup query_band value to NONE and
resubmit.

9889 Session currently loading other LDI tables.
Explanation: A BEGIN ISOLATED LOADING command is submitted in a session that is currently already a load session.
The session is performing a concurrent isolated load already.
Generated By: Resolver modules.
For Whom: End user.
Remedy: After the on-going load operation is completed, set the LDILoadGroup query_band value to NONE, issue the
SET QUERY_BAND command and then resubmit the BEGIN ISOLATED LOADING command.

9890 Table %DBID.%TVMID is not load isolated.
Explanation: There are multiple reasons for this error. 1) A BEGIN ISOLATED LOADING specifies a table that is either
not a LDI table or a LDI table on which concurrent isolated loading is disabled. 2) TD_ROWLOADID is specified on a non-
LDI table 3) ALTER TABLE with RELEASE DELETED ROWS option is submitted on a non-LDI table.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Check the command for correct LDI table and resubmit the command.

Above are list of Teradata Errors or Failure Codes from Error 9881 To 9890 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.

 
1 2 3 50