Teradata SQL Error and Failure Codes from Error 3706 To 3714

3706 Syntax error: %VSTR.
Explanation: The request contains a syntax error. ’%VSTR’ identifies the approximate location of the error or identifies
the syntax problem.
Generated By: SYN modules.
For Whom: End User.
Notes: The failure parcel INFO field contains the character position of the error location in the request parcel.
In addition to syntax errors, this error message may also indicate a problem such as: duplicate index or constraint names,
misspelled function names or function parameters, or cast to an invalid or non-existent data type.
Remedy: Correct the syntax and resubmit the request.

3707 Syntax error, expected something like %VSTR.
Explanation: The request contains a syntax error. ’%VSTR’ identifies what the syntaxer expected to encounter.
Generated By: SYN modules.
For Whom: End User.
Notes: The failure parcel INFO field contains the character position of the error location in the request parcel.
Although the Teradata SQL Parser tries to identify the exact error and show how to correct it, it cannot always give the right
solution because it does not know the user’s intent.
Remedy: Correct the syntax and resubmit the request.

3708 Syntax error, %VSTR should be deleted.
Explanation: The request contains a syntax error. The syntaxer did not expect ’%VSTR’.
Generated By: SYN modules.
For Whom: End User.
Notes: The failure parcel INFO field contains the character position of the error location in the request parcel.
Although the Teradata SQL Parser tries to identify the exact error and show how to correct it, it cannot always give the correct
solution because it does not know the user’s intent.
Remedy: Correct the syntax and resubmit the request.

3709 Syntax error, replace %VSTR.
Explanation: The request contains a syntax error. ’%VSTR’ represents the field that should be substituted.
Generated By: SYN modules.
For Whom: End User.
Notes: The failure parcel INFO field contains the character position of the error location in the request parcel.
Although the Teradata SQL Parser tries to identify the exact error and shows how to correct it, it cannot always give the
right solution because it does not know the user’s intent.
Remedy: Correct the syntax and resubmit the request.

3710 Insufficient memory to parse this request, during %VSTR phase.
Explanation: The request was more complex than the Teradata SQL Parser could process. The parser stopped at the indicated
phase.
Generated By: NEO modules.
For Whom: End User.
Remedy: Increase the DBS Control Record field MaxParseTreeSegs. See Teradata Database Design manual.
Otherwise, 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.

3711 Memory segment unavailable to parse this request, %VSTR phase.
Explanation: An attempt to get a memory segment failed while parsing a Teradata SQL statement. The parser stopped at
the indicated phase.
Generated By: NEO modules.
For Whom: End User.
Remedy: Normally, 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 script to your support representative.

3712 Insufficient memory for Plastic Steps for this request.
Explanation: The request was more complex than the Teradata SQL Parser could process. The parser stopped during
generation of ’Plastic Steps’ which must fit within two segments of memory. A single ’Plastic Step’ must fit within one segment.
Generated By: GEN modules.
For Whom: End User.
Remedy: Increase the DBS Control Record field StepsSegmentSize. See Teradata Utilities Manual for information on DBS
Control fields. Otherwise, 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 script to your support representative.

3713 A call to change a memory segment size failed during parsing.
Explanation: An attempt to change the size of a memory segment failed while parsing a Teradata SQL statement.
Generated By: MGC, OPT and GEN modules.
For Whom: System Support Representative.
Remedy: If the problem persists, notify your support representative.

3714 Insufficient memory for a Concrete Step for this request.
Explanation: The request was more complex than the Teradata SQL Parser could process. The parser stopped during
generation of a ’Concrete Step’ which must fit within one segment of memory or request generated too many concrete steps
segments.
Generated By: OPT modules.
For Whom: End User.
Remedy: Normally, 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 script to your support representative.

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