Teradata SQL Error and Failure Codes from Error 6706 To 6716

6706 The string contains an untranslatable character.
Explanation: The ISF subsystem encountered an untranslatable character while importing, or internally moving, a character string.
Generated By: The ISF subsystem translation routines.
For Whom: End User.
Remedy: Either your SQL statement, or your data, has some invalid characters. If the name of the translation is known,
use the TRANSLATE_CHK to point to the bad character. Correct and resubmit.

6707 Internal error: A move of overlapping strings was requested of the ISF subsystem.
Explanation: The string locations and lengths overlap in one of the following ways:
1) Character strings which completely overlap (the starting locations of both strings are the same) and the strings will change size during translation.
2) Byte, character, or ynet strings which partially overlap.
Generated By: The ISF subsystem. Most likely the isfchar, isfbyte, or or isfynet routines.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6708 Internal error: Occurred while the ISF subsystem was installing character translation tables.
Explanation: The ISF subsystem encountered an internal error while installing character set, or internal, translation
tables.
Generated By: The ISF subsystem init routines.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6709 Internal error: No memory was available for the ISF subsystem to perform the move.
Explanation: The character string move which was requested requires the allocation of a temporary memory buffer and
no memory is available.
Generated By: The ISF subsystem, or routines which call ISF.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

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

6711 Internal error: Collation input file invalid.
Explanation: An input file defining collation has an unexpected format. Most likely, the file(s) in /tpasw/etc is(are) corrupted.
Generated By: isfreadcoll
For Whom: Support Representative.
Remedy: Try pkgadd. If the problem persists, notify Remedy: If the problem persists, notify your Support Representative.

6712 Internal error: Ocurred during ISF subsystem collation initialization.
Explanation: Collation initialization could not complete.
Generated By: The ISF subsystem routines for collation initialization.
For Whom: Support Representative.
Remedy: Notify your Support Representative.

6713 Internal error: Collation input file ambiguous.
Explanation: Collation initialization has detected a character defined to sort in two different places. One of the collation
files is broken.
Generated By: isfreadcoll
For Whom: Support Representative.
Remedy: Notify your Support Representative.

6714 Internal error: Reference to undefined value in collation file.
Explanation: Collation initialization has detected a reference to a character which has not been defined. One of the collation
files is broken.
Generated By: isfreadcoll
For Whom: Support Representative.
Remedy: Notify your Support Representative.

6715 Collation memory limit exceeded. Install fewer character sets.
Explanation: The collation GDO is not large enough to handle all the collations being loaded. This is probably due to
CHARSET_COLL requiring a new collation for every loaded character set.
Generated By: The ISF subsystem routines for collation initialization.
For Whom: The DBA.
Remedy: Reduce the number of character set translations to be installed.

6716 Internal error: Expected collation input file could not be opened.
Explanation: A file required for proper collation initialization can not be opened, probably because it does not exist
where it should be–/tpasw/etc.
Generated By: The ISF subsystem routines for collation initialization.
For Whom: Support Representative.
Remedy: Try pkgadd. If the problem persists, notify your Support Representative.

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