Teradata SQL Error and Failure Codes from Error 5639 To 5649

5639 Request size exceeds Parser limit of 1048500 bytes.
Explanation: The user specified a request that exceeds the specified limit.
Generated By: Parser modules
For Whom: End user
Remedy: The request size in bytes exceeds the limit imposed by the system. Check the request, correct and re-submit.

5640 The QCD version does not match the expected ’%VSTR’ version.
Explanation: The version of the specified Query Capture Database (QCD) is not supported by the currently running version
of the Teradata DBS. * <- DR113879-sb230098-01 *
Generated By: Parser
For Whom: End User. * DR113879-sb230098-01-> *
Remedy: Specify a QCD whose version is compatible with the running version of the Teradata DBS Software. * <-
DR113879-sb230098-01 *

5641 Conflicting QCD names specified in index validation mode.
Explanation: This error occurs when the QCD does not match with the QCD a name specified in the index validation
mode.
Generated By: Parser
For Whom: End User.
Remedy: Use the same QCD name through out the index validation mode.

5642 Invalid diagnostic level.
Explanation: This error occurs when the DIAGNOSTIC ValidateIndex is specified at a level other than SESSION.
Generated By: Parser
For Whom: End User.
Remedy: Submit the statement with only Session Level

5643 Invalid request in index validation mode. %VSTR
Explanation: The submitted SQL request is not permitted during an index Wizard Validation session. Only the following
types of statements are permitted: CREATE | DROP INDEX, CREATE JOIN INDEX, ALTER TABLE, COLLECT STATISTICS
, and INSERT EXPLAIN. * <- DR113879-sb230098-01 *
Generated By: Resolver
For Whom: End User. * DR113879-sb230098-01-> *
Remedy: Remove the unsupported statement or execute the statement outside of Validation mode. The VSTR may contain
additional information about the specific feature that is not permitted. * <- DR113879-sb230098-01 *

5644 No match found for specified tables in the request.
Explanation: The table list specified in the WITH STATISTICS FOR <TableList> in the INSERT EXPLAIN SQL statement
are not referenced in the request.
Generated By: RES modules.
For Whom: End User.
Remedy: Check the tables, correct the list and resubmit the request.

5645 The value of ’%VSTR’ supplied is out of range.
Explanation: A user specified parameter for an Index Wizard Analysis statement has a value that is outside the permitted
range The VSTR should identify the offending parameter. * <- DR113879-sb230098-01 *
Generated By: Parser
For Whom: End-User * DR113879-sb230098-01-> *
Remedy: Correct the parameter value. * <- DR113879-sb230098-01 *

5646 User does not match user ’%FSTR’ who performed the index anlaysis.
Explanation: The user who restarted the index analysis must be the same as the user who executed the SQL INITIATE
INDEX ANALYSIS statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Login as the specified user to restart the index analysis.

5647 Internal erorr: Data dictionary table UDFInfo in inconsistent state.
Explanation: The information listed in the UDFInfo data dictionary table is inconsistent with the information listed in
TVM table. This is an internal error.
Generated By: RES modules.
For Whom: Field Engineer
Remedy: Check the data in UDFInfo and TVM, and correct the problem.

5648 Too many parameters for a function.
Explanation: The maximum number of function parameters is 128. If user has specified over 128 parameters in a create
function statement, this error is generated.
Generated By: RES modules.
For Whom: End User
Remedy: Correct the statement and resubmit the request.

5649 The UDF/XSP “%VSTR” is invalid.
Explanation: The UDF/XSP the user is attempting to use is not compatible with the current platform. It must be recompiled
first and possibly modified to work on the new platform.
Generated By: RES modules.
For Whom: DBA
Notes: This code can be returned as a warning during the compilation of UDFs after a restore for a function from pre-
TD12.0 DBS. The function table header is converted and it must be modified to work on the new platform. This error is returned if the user tries to ALTER COMPILE a UDF/XSP that does not have any source code (for instance if it
is defined with an object, a package, or a library file) and the UDF/XSP has been migrated across platforms
Remedy: When reloading a UDF/XSP from an archive onto another platform, the UDF/XSP must be recompiled in
order to be run on the new platform. See the ALTER FUNCTION/PROCEDURE statement to recompile the UDF/XSP.

Above are list of Teradata Errors or Failure Codes from Error 5639 To 5649 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 *