Teradata SQL Error and Failure Codes from Error 3727 To 3739

3727 Data format length must match target character length for %VSTR.
Explanation: When converting numeric or date data to character during a FastLoad job the length of the formatted
string after the data has been processed through the format must match the length of the target character field. The format
can be an explicit or a default format.
Generated By: OPT modules.
For Whom: Host Utility Fast Load.
Remedy: Correct the format and resubmit the request.

3728 A non-numeric column or expression cannot have range clause.
Explanation: The non-numeric column or expression cannot have a range clause.
Generated By: SYN modules.
For Whom: End User.
Remedy: Eliminate the range clause and resubmit the request.

3730 The user used an obsolete syntax or feature in this request.
Explanation: This code is a warning only, not an error. It means that the user used an old form for a statement that is considered
obsolete. There is a newer form that should be used.
Generated By: LEX and PAR modules.
For Whom: End User.
Remedy: This message is for information only.

3731 The user must use IS NULL or IS NOT NULL to test for NULL values.
Explanation: The user tried to use a comparison operator with the NULL constant (for example: X=NULL). This does
not make sense, since any comparison against NULL cannot be true. Therefore, the comparison will never return rows.
Generated By: SYN modules.
For Whom: End User.
Remedy: Use the syntax IS NULL or IS NOT NULL to test for null values.

3732 The facility of %VSTR has not been implemented yet.
Explanation: The indicated functionality has not yet been implemented. It may be implemented in some future release.
Generated By: SYN modules.
For Whom: End User.
Remedy: Modify the statement to use implemented features andresubmit. If the feature is documented as available,
notify your support representative.

3733 The SELECT has more than one %VSTR clause.
Explanation: The SELECT statement contained more than one WHERE clause, ORDER BY clause, or ALIAS clause.
Generated By: SYN modules.
For Whom: End User.
Remedy: Correct the syntax of the SELECT statement and resubmit the request.

3734 Internal error: Unexpected result from FLT subsystem.
Explanation: While using the FLT subsystem, the parser received an unexpected error.
Generated By: LEX and RES modules.
For Whom: System Support Representative.
Remedy: If the problem persists, notify your support representative.

3735 Title string is longer than ’%VSTR’ characters.
Explanation: Titles must be no more than 256 characters.
Generated By: SYN modules.
For Whom: End User.
Remedy: Correct the statement to have a shorter title, and resubmit the request.

3736 FORMAT string is longer than 30 characters.
Explanation: Picture formats cannot be more than 30 characters.
Generated By: SYN modules.
For Whom: End User.
Remedy: Correct the statement to have a shorter format, and resubmit the request.

3737 Name requires more than 30 bytes in %VSTR internal form.
Explanation: Names in DBS/SQL cannot be longer than 30 after translation to Latin, or Kanji, internal form. Note that
with Unicode character sets, a name may be longer than 30 bytes in the session character set and less than 30 bytes after
translation to internal form. For example, this valid name “Mynameislongandhasa_eurosign_?” has 30 characters and is
encoded in Latin with 30 bytes, UTF16 with 60 bytes, and UTF18 with 32 bytes;
Generated By: LEX, PAR and OPT modules.
For Whom: End User.
Remedy: Correct the statement to have a shorter name, and resubmit the request.

3738 String is longer than 31000 characters.
Explanation: Quoted strings cannot be longer than 31000 physical characters.
Generated By: LEX modules.
For Whom: End User.
Notes: To insert longer strings, the user must have a USING clause and a DATA parcel that contain the characters.
Remedy: Correct the statement to have a shorter string, and resubmit the request.

3739 The user must give a data type for %VSTR.
Explanation: A field in a CREATE TABLE statement, a USING definition, or a macro parameter definition did not specify
the data representation of the object.
Generated By: SYN modules.
For Whom: End User.
Notes: The data representations are:BYTEINT SMALLINT INTEGER DECIMAL(n,m) FLOAT CHAR(n) VARCHAR(n) LONG VARCHAR BYTE(n) VARBYTE(
n) GRAPHIC(n) VARGRAPHIC(n) LONG VARGRAPHIC(n)
Remedy: Correct the statement to have the data type and resubmit the request.

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