Teradata SQL Error and Failure Codes from Error 3888 To 3901

SQLServerF1_Header_Small

3888 A SELECT for a UNION,INTERSECT or MINUS must reference a table.
Explanation: A SELECT phrase which is part of a UNION, INTERSECT, or MINUS query must reference at least one
table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the request and resubmit the request.

3889 Too many USING clauses in a request.
Explanation: The request should only contain one USING clause. The USING clause should usually be part of the first
statement in the request.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the request and resubmit the request.

3890 Macro ’%VSTR’ cannot refer to itself.
Explanation: The macro being created or replaced cannot refer to itself in the body of the macro.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the request and resubmit the request.

3891 Check text for check constraint (explicit or derived from partitioning expression) is greater than %VSTR characters.
Explanation: The text of the check exceeded the maximum length characters. Note that the check could be an implicit
check constraint derived from the partitioning expressions for an index. For column constraint check, the maximum length
is 8192 characters. For table constraints and named constraints, the maximum length is 16000 characters.
Generated By: RES and OPD modules.
For Whom: End User.
Remedy: Shorten the check constraint or partitioning expressions and resubmit the request.

3894 Too many tables specified in BEGIN/RELEASE MLOAD.
Explanation: The Begin MLoad statement contains more five tables.
Generated By: OPT modules.
For Whom: End User.
Remedy: Resubmit request with five or less tables.

3895 Internal error: Quiesce message preceded in-doubt session loading.
Explanation: ConTsk cannot process a quiesce message until it has finished loading in-doubt sessions. This error occurs
after an SPR, and usually signifies a lost message.
Generated By: ConTsk.
For Whom: System Support Representative.
Remedy: Save all information. Contact your support representative

3896 Statement caused parser stack overflow.
Explanation: The request was more complex than the Teradata SQL Parser could process.
Generated By: PAR modules.
For Whom: End User.
Remedy: Simplify the statement and resubmit the request.

3897 Request aborted due to Teradata system restart. Resubmit.
Explanation: The Optimizer phases of the Teradata SQL Parser caused a restart during the processing of the request.
Generated By: ITB modules.
For Whom: End User.
Remedy: Resubmit the transaction.

3898 Internal error: Cannot quiesce a session already quiesced.
Explanation: Either 2PC or the Performance Monitor tried to quiesce a session that was already quiesced.
Generated By: ConTsk.
For Whom: System Support Representative.
Remedy: Save all information. Contact your support representative.

3899 Internal error in the Teradata SQL Parser.
Explanation: The Teradata SQL Parser erred.
Generated By: CON, LEX, PAR, SYN, RES and OPT modules.
For Whom: System Support Representative.
Notes: This is usually caused by a request that the Teradata SQL Parser could not correctly process, yet it did not detect
an error.
Remedy: Save all relevant information and notify your support representative.

3900 User error detected.
Explanation: The Teradata SQL Parser erred.
Generated By: PAR and RES modules.
For Whom: System Support Representative.
Notes: This error should never be reported to a user. The actual user error code is TSeg.Ptr@.Errinfo.Code.
Remedy: Save all relevant information and notify your support representative.

3901 Session is already logged on.
Explanation: Session control has sent the parser a logon request for a session that is already logged on.
Generated By: CON modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

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