Teradata SQL Error and Failure Codes from Error 3697 To 3705

SQLServerF1_Header_Small

3697 Attempt to translate Unicode/Graphic/KanjiSJIS data to another form has failed
Explanation: This error occurs if a Multi-Byte Character (MBC) string, GRAPHIC string, or GRAPHIC data contains
MBC data that has either an odd number of bytes (contains SBC), or there are invalid codes. Either your SQL statement, or
your data, has badly formed MBCs data.
Generated By: LEX, OPD, OPU DR56128-cnb-01
For Whom: End User and/or Internal DR56128-cnb-01
Notes: None.
Remedy: Correct and resubmit. Contact support representative if the problem persists */ /*DR56128-cnb-01

3698 SysSecDefaults table has a negative value in an integer column.
Explanation: All values in the integer columns of the SysSecDefaults table must be either 0 or a positive value.
Generated By: MgcSecOp.
For Whom: Site Administrator.
Remedy: Correct the value for the column in the table SysSecDefaults and restart Teradata.

3699 SysSecDefaults table has an invalid character value in a char column.
Explanation: The character value in the PasswordDigits column of the table SysSecDefaults must be either a ’N’ to indicate
no (not allowed), an ’Y’ to indicate yes (allowed but not required), or ’R’ to indicate required.
The character value in the PasswordSpecChar column of the table SysSecDefaults must be within the range of ’A’ – ’P’, ’R’,
or ’Y’ as defined by the matrix below. This single character field represents the setting of four password control rules: 1)
UserName allowed within the password string 2) Upper/Lower case characters within the password string 3) At least one
alpha character within the password string 4) Special characters within the password string
In the matrix below, to the right of each valid option character is a single character (Y, N, or R) to indicate how each of the
four password control rules are set. ’N’ indicates not allowed, ’Y’ indicates allowed but not required (for rule Upper/Lower
it means ignore case), and ’R’ indicates required.
Upper/ One Spec Option UserName Lower Alpha Chars N Y Y Y N Y Y Y Y Y A Y Y Y R B Y Y R N C Y Y R Y D Y Y R R E
Y R R N F Y R R Y G Y R R R H N Y Y N I N Y Y Y J N Y Y R K N Y R N L N Y R Y M N Y R R O N R R N P N R R Y R N R
R R
Generated By: MgcSecOp.
For Whom: Site Administrator.
Remedy: Correct the value for the column in SysSecDefaults and restart Teradata.

3700 Internal error: An assertion failed.
Explanation: This error occurs only if an inconsistency was detected by the syntaxer. For example, the tables do not
match the version in the syntaxer.
Generated By: SYN modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and the dump, and contact your support representative

3701 Internal error: An unknown error has occurred.
Explanation: If this error occurs, an inconsistency was detected by the Teradata Parser code.
Generated By: MGC, OPT and GEN modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and the dump, and contact your support representative.

3702 Insufficient memory to parse this request.
Explanation: The request was more complex than the Teradata Parser could process.
Generated By: MGC, SYN, RES, OPT and GEN modules.
For Whom: End User.
Remedy: Simplify the request and resubmit it.

3703 ’%FSTR’ is a Teradata SQL keyword reserved for future use.
Explanation: The request contained a reserved keyword.
Generated By: LEX modules.
For Whom: End User.
Remedy: Choose a different name and resubmit the request.

3704 ’%FSTR’ (’%VSTR’X) is not a valid Teradata SQL token.
Explanation: The specified character is not a Teradata SQL token. The hexadecimal equivalent of the character is shown
in parentheses. The hex equivalent is useful if a character is unprintable.
Generated By: LEX modules.
For Whom: End User.
Remedy: Check the quoted string for proper matching, or remove the invalid character.

3705 Request executed in interpretive EVL mode.
Explanation: This is a warning only, not an error. It indicates that the current request will be executed using interpretive
EVL code rather than executable EVL code. Cases where this warning will be returned are:
a) Ran out of parser tree segments when trying to generate the executable EVL code.
b) Ran out of Plastic Step segment when trying to fit both interpretive EVL code and executable EVL code in the Plastic
Steps.
c) Ran out of space in the concrete step segment when building one large single step. In an attempt to save space, the compiled
is replaced with the interpretive EVL code. The only remedy is to simplify the query.
Generated By: GNCStEvl, GncApply.
For Whom: DBA User and System Support Representative.
Note: The request is still processed despite the warning.
Remedy: This message is for information only. To avoid the warning, user may increase the DBS Control Record field
MaxParseTreeSegs for case (a) and field StepsSegmentSize for case (b). See Teradata Utilities Manual for information on
DBS Control fields.

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