Teradata SQL Error and Failure Codes from Error 3492 To 3505

SQLServerF1_Header_Small

3492 The request context could not be located.
Explanation: The request context could not be located.
Generated By: thdxutil
For Whom: Support Representative.
Notes: None.
Remedy: Contact your Support Representative.

3493 Bad thread timeout detected by application.
Explanation: The application detected a bad thread timeout.
Generated By: thdx7
For Whom: Support Representative.
Notes: One of the EXMTest7 tests detected an error.
Remedy: Contact your Support Representative.

3494 Bad thread detected by application.
Explanation: The application detected a bad thread.
Generated By: thdx7
For Whom: Support Representative.
Notes: One of the EXMTest7 tests detected an error.
Remedy: Contact your Support Representative.

3500 Parser does not recognize this SQL statement.
Explanation: This error occurs only if code is missing from the database Parser.
Generated By: OPT modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and the dump, and contact your support representative.

3501 Internal error: Statement or subquery expected and not found.
Explanation: This error occurs if the Resolver expects a statement list, a statement, or a subquery in the parse tree and some other node occurs.
Generated By: RES modules.
For Whom: System Support Representative.
Notes: This is not a user error.
Remedy: Save all relevant information and the dump, and contact your support representative.

3502 Internal error: A non-statement node was in a statement list.
Explanation: This error occurs if a statement list has an invalid subnode, not indicating a statement, in the optimizer or
code gen phase of the Teradata SQL Parser.
Generated By: RES, OPT and GEN modules.
For Whom: System Support Representative.
Notes: This is not a user error.
Remedy: Save all relevant information and the dump, and contact the your support representative.

3503 Internal error: Statement list required but not found.
Explanation: This error occurs if a bug or code mismatch was in the resolver or optimizer.
Generated By: RES and OPT modules.
For Whom: System Support Representative.
Notes: This is not a user error.
Remedy: Save all relevant information and the dump, and contact the your support representative.

3504 Selected non-aggregate values must be part of the associated group.
Explanation: This error occurs when an aggregate query includes a non-aggregate expression in the SELECT list,
WHERE clause, ORDER BY clause, HAVING clause or WITH list that is not also exactly specified in the corresponding
GROUP BY or WITH…BY clause.
Note that we also return this error when ORDER BY and WITH clauses contain aggregates but the query does not.
Generated By: OPT modules.
For Whom: End User.
Notes: For example, it is not legal to:
SELECT State GROUP BY ZipCode; .
In order for the request to be legal, it may be changed to:
SELECT State GROUP BY State, ZipCode; .
It is also not legal to:
SELECT StateNo WITH SUM(StateNo) ORDER BY SUM(StateNo) ;
A legal request is:
SELECT SUM(StateNo) WITH SUM(StateNo) ORDER BY SUM(StateNo) ;
Remedy: Correct the request and resubmit it.

3505 Match Tag Parcel missing in Mload.
Explanation: INSERT, UPDATE, and DELETE statements issued during MLOAD processing must be accompanied by
MatchTag parcels. Either the user is in- advertently in MLOAD and has sent a normal query or the MLOAD query has
somehow omitted the MatchTag Parcel.
Generated By: GEN modules.
For Whom: User.
Remedy: Insure that DML statements, INSERT, UPDATE, and DELETE, are only sent with MatchTag
Parcels. This should occur automatically with normal use of the MLOAD Utility

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