Teradata SQL Error and Failure Codes from Error 6731 To 6757

SQLServerF1_Header_Small

6731 Internal error: Allocated space is not sufficient for target name.
Explanation: In the ISF subsystem, the amount of space indicated by an input parameter is not sufficient in order to create
the target object name.
Generated By: The ISF subsystem.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6732 Internal error: Wildcard string or name is not uppercased or not normalized.
Explanation: In the ISF subsystem, the wildcard string or the object name to be compared against it is either not uppercased
or not normalized.
Generated By: The ISF subsystem.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6733 Character set specified for name validation rule in DBCControl is invalid. Only minimal name validation is enforced.
Explanation: The character set number for the name validation rule specified in DBCControl does not correspond to a
character set that was actually loaded by the database. Database will operate as if name validation rule was set to 0 (any
valid name is allowed).
Generated By: The ISF subsystem.
For Whom: End User.
Remedy: Check to see if the character set is marked for loading in DBC.CharTranslations or if there is another message in
the log indicating the character set was not loaded. Correct any problems with the character set being loaded, or change the
name validation rule to refer to a loaded character set.

6750 Invalid date.
Explanation: This error occurs when the specified date is invalid. For instance, dates like ’12/35/2001’ (format
’mm/dd/yy’) (35 days are invalid) or ’14/12/2001’ (format ’mm/dd/yy’) (14 months are invalid) result in this error.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct the date and resubmit the request.

6751 Invalid date format.
Explanation: This error occurs when specified date format string is invalid.For instance,date format strings like ’D5-
MMM-YY’ (’D5’ is invalid) or ’DD-MMMMM-YYYY’ (’MMMMM’ is invalid) result in this error.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct the date format string and resubmit the request.

6752 Illegal format type specified : %VSTR must be of numeric or date format type.
Explanation: This error occurs when the format type is time or timestamp. TDI API tdic_fmtscan accepts format strings
of type numeric or date only.
Generated By: TDI modules.
For Whom: End user.
Remedy: Check the type of the format string.

6753 The date does not correspond to an existing era.
Explanation: The format string of a date column contains the Japanese Imperial Era indicator, but the given date does
not correspond to any of the Japanese Imperial Eras.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct the date and resubmit the request.

6754 Bad option with tdlocaledef utility.
Explanation: This error occurs when a bad option is specified with tdlocaledef utility. For instance, when a pre-V2R5
option is specified, -input cannot be used and only -output new has to be specified.
Generated By: TDI modules.
For Whom: End user.
Remedy: Check the options specified and recompile the tdlocaledef utility.

6755 Invalid data in SDF.
Explanation: This error occurs when an invalid data is specified in the SDF as input to tdlocaledef utility. For instance,
radix and group separators cannot be more than one character long; and all 7 days have to be specified for short/long days.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct data in the SDF text file and recompile SDF via tdlocaledef utility.

6756 Null string is not allowed in %VSTR.
Explanation: This error occurs when a null string is specified in the SDF. For instance, grouping rule or radix separator
or currency Name, etc. (any data in SDF) cannot be null.
Generated By: TDI modules.
For Whom: End user.
Remedy: Correct data in the SDF and recompile SDF via tdlocaledef utility.

6757 Output file %VSTR is not written completely.
Explanation: This error occurs when data is not copied completely to output file name specified by tdlocaledef utility.
Generated By: TDI modules.
For Whom: End user.
Remedy: Recompile tdlocaledef utility.

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