Teradata SQL Error and Failure Codes from Error 6717 To 6730

SQLServerF1_Header_Small

6717 Internal error: Unexpected character set for comparison.
Explanation: The CharType can not be handled by this routine. It should have been converted earlier.
Generated By: fltevcmp or msccmpd.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6718 Internal error: Character sets do not match for comparison.
Explanation: Character data from different character sets should have already been converted before being seen by the
current routine.
Generated By: fltevcmp or msccmpd
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6721 Internal error: Occurred during translation of dictionary object names or text strings.
Explanation: The MGC, or FLD, subsystems encountered an internal error during translation of an object name or text
string in the data dictionary. Translation is attempted between the Unicode form on disk and the internal Latin, or Kanji1,
form in memory.
Generated By: The MGC, or FLD, subsystem routines.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6723 STATEMACHINE S80 is no longer supported.
Explanation: The map file for the specified session character set has STATEMACHINE S80, which is no longer supported.
STATEMACHINE S81 will be used instead. This means that any multibyte characters that start with 0x80 will not
be translated correctly.
Generated By: isfinitsdcx
For Whom: The DBA.
Remedy: This is just a warning. Specifying STATEMACHINE S81 in the appropriate map file will remove the warning.

6724 The object name is too long in NFD/NFC.
Explanation: During the name validation, the ISF subsystem calculated the length of a name string and it is longer than
128 characters in NFD/NFC. The object name must not exceed 128 characters when converted to NFD/NFC.
Generated By: The ISF subsystem.
For Whom: End User.
Remedy: The input name string is longer than 128 characters in NFD/NFC. Correct and resubmit the SQL.

6725 Object name contains restricted characters.
Explanation: Characters that are excluded by the Name Validation Rules in DBS control settings have been detected in
an object name. Note that all settings exclude the following characters: U+0000, U+001A, U+FFFD, U+FA6C, U+FACF, U+FAD0, U+FAD1, U+FAD5, U+FAD6, and U+FAD7. Characters that are converted to NFC, uppercased and are not contained
in the client character set are also excluded.
Generated By: The ISF subsystem.
For Whom: End User.
Remedy: Either your SQL statement or your data has one or more restricted characters in the name string. Correct and
resubmit the SQL or contact your DBA about changing the Name Validation Rules.

6726 Internal error: ICU normalization function threw an error during the Unicode Normalization process.
Explanation: When transforming a string into one of the Unicode Normalization Forms, an ICU normalization API has
thrown an error. We should never get into this scenario, but we can use this error for debugging purpose.
Generated By: The ISF subsystem.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6727 Internal error: Occurred during ISF EON subsystem processing.
Explanation: The ISF EON subsystem encountered an internal error.
Generated By: The ISF subsystem.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6728 Internal error: Memory pool ID is invalid.
Explanation: In the ISF subsystem, the pool ID used to initialize a memory pool is not in the valid range, or a pool ID not created by the caller thread has been referenced.
Generated By: The ISF subsystem.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6729 Internal error: Session character set is invalid.
Explanation: In the ISF subsystem, the session character set passed is not in the valid range.
Generated By: The ISF subsystem.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6730 Internal error: Pool memory limit is exceeded.
Explanation: In the ISF subsystem, the memory pool referenced has exceeded its memory limit.
Generated By: The ISF subsystem.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

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