Teradata SQL Error and Failure Codes from Error 6758 To 6767

6758 Invalid time.
Explanation: This error occurs when the specified time is invalid. For instance, time values like ’14:20:22 AM’ (format
HH:MM:SSBT’) (Formatting element ’T’ means 12-hour clock, which means the hours component value cannot exceed 12)
or ’27:90:22’ (format HH:MM:SS’) (27 hours and 90 minutes are both invalid) result in this error.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct the time and resubmit the request.

6759 Invalid time format string.
Explanation: This error occurs when the specified time format is invalid. For instance, time format strings like ’HHHMMMSSs’ (h,m,s separators have to be specified using small letters only) or ’HH:MM:SS.S(16)’ (Fractional seconds should be in the range 0-6 only) result in this error.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct the format string and resubmit the request.

6760 Invalid timestamp.
Explanation: This error occurs when the specified timestamp is invalid. For instance, timestamp values like ’25-12-2001
26:18:22 AM’ (format ’DD-MM-YYYYBHH:MM:SSBT’) (26 hours is invalid) or ’32-01-2001 04:05:05’ (format ’DD-MMYYYYBHH:
MM:SS’) (32 days are invalid) result in this error.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct the timestamp value and resubmit the request.

6761 Invalid timestamp format string.
Explanation: This error occurs when the specified timestamp format string is invalid. For instance, timestamp format
strings like ’E3-E4-M3-YYYY HH:MM’ (Both ’E3’ and ’E4’ cannot come together) or ’E3-MM-YY HHH:MMm’ (h,m,s separators
have to be specified using small letters only) result in this error.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct timestamp format string and resubmit the request.

6762 DateTime field overflow.
Explanation: This error occurs when a TDI module cannot represent a time or timestamp value with its defined precision.
For instance, if the fractional seconds in a time format string have a precision of 3 (hh:mm:ss.s(3)), and the data is
07:30:15.56723 (precision is 5 here), this error is reported.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct the precision value for time/timestamp and resubmit the request.

6763 File %VSTR does not exist.
Explanation: This error occurs when a file specified by tdlocaledef does not exist. For instance, the user may specify a file name with -input or -output or -reverse option in tdlocaledef utility. When this file does not exist, the above error is reported.
Generated By: TDI modules.
For Whom: End user.
Remedy: Check the file name or path and recompile tdlocaledef utility.

6764 Illegal token in the SDF data.
Explanation: This error occurs when an invalid token is specified in the SDF data file. For instance, short, long, dual, etc. are all invalid tokens.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct data in the SDF file and recompile SDF via tdlocaledef utility.

6765 Input SDF data contains characters that are not in the Unicode repetoire.
Explanation: This error occurs when the translation to Unicode fails. The Unicode characters are represented using
u<hex number> in the SDF in the form of 7-bit Ascii. These Ascii characters inside the SDF are converted to Unicode and
then stored in the TDI GDO. During this conversion, if any Unicode character or group of characters including the digits 0- 9 or blank space character or the characters below 0x009F range are found, this error is reported.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct data in the SDF file and recompile SDF via tdlocaledef utility.

6766 Syntax error in SDF.
Explanation: This error occurs when there is an error in the syntax of SDF file. For instance, short days or long days not specified within double quotes or not separated by “;” are considered to be syntax errors.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct the syntax, and recompile the SDF via tdlocaledef utility.

6767 Invalid numeric data.
Explanation: This error occurs when the numeric data specified is invalid. For instance, numeric data such as ’123+.34’, ’12$.56’, ’123..57’ result in this error.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct the numeric value and resubmit the request.

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