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.