Teradata SQL Error and Failure Codes from Error 6697 To 6705

6697 Fatal error in RSG.
Explanation: RSG received an unexpected error which caused the Teradata DBS to crash. Resubmitting the operation
will probably cause another system crash.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: The crash is caused by a Teradata DBS error. Contact your Support Representative.

6698 The Message Size in RSG exceeded the maximum limit.
Explanation: The Message Size exceeded the maximum limit of 256K bytes in length.
Generated By: RSG
For Whom: Intermediary/End User
Remedy: Contact your Support Representative.

6699 Transaction aborted due to replication transport outage.
Explanation: RSG got a disconnect from transport in maximum potection mode. Therefore transaction was aborted.
Any new transaction will all be aborted until a reconnection happens from the transport.
Generated By: RSG
For Whom: End User
Remedy: Re-establish connection.

6700 Internal error: A move between incompatible string types was requested of the ISF subsystem.
Explanation: Is returned when a move of a byte, character or ynet string to an incompatible destination string is
requested. This is possibly caused by a mismatch of strings types. For example, moving a byte string to a character string.
Generated By: The ISF subsystem. Most likely the isfcalc routine.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6701 An unknown character string translation was requested.
Explanation: The ISF subsystem was requested to perform an unknown translation. It is likely that the translation name
given in the TRANSLATE function is invalid, or the character set required for the translation has not been installed.
Generated By: The ISF subsystem, or flttrans routines.
For Whom: End User.
Remedy: Correct the translation-name in the statement and resubmit it. Install the required character set as
This error can also be returned when importing or exporting a character string to a client character set. For example, a translation from ASCII to GRAPHIC is an unknown translation. Change the session character set, or internal character data type, in the statement and resubmit it. If this doesn’t help, contact your Support Representative.

6702 Translation from/to a character string with an invalid character set specification was requested of the ISF subsystem.
Explanation: The ISF subsystem has detected a client character set which is invalid, or not loaded. It is likely that the character set was passed in the system message header. The TDP, or gateway, may not be operating properly.
Generated By: The ISF subsystem. Most likely the isfcalc routine.
For Whom: End User.
Remedy: Try resetting TDP by issuing .SET SESSION CHARSET <charsetname> command (if you use BTEQ). <charsetname>
must be a valid character set. ASCII & EBCDIC are guaranteed to be valid. If this doesn’t help, contact your Support
Representative.

6703 Internal error: A move from, or to, an unknown string type was requested of the ISF subsystem.
Explanation: Is returned when a move involving non-string data is requested. The valid string types are: byte, character
and ynet. This is possibly caused by passing a numeric type in the evlrepresent argument.
Generated By: The ISF subsystem. Most likely the isfcalc routine.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6704 Internal error: The ISF subsystem was requested to export a string to the client which is too large.
Explanation: Is returned when the string exported to the client is larger than the maximum allowed string size.
Generated By: The ISF subsystem. Most likely the isfcalc routine.
For Whom: Support Representative.
Remedy: If the problem persists, notify your Support Representative.

6705 An illegally formed character string was encountered during translation.
Explanation: This error occurs when in a string containing Multi-Byte Characters (MBC), the MBCs are not completely
formed. The possibilities are:
Form-of-use Illegal characters ———– ——————
Unicode Any single-byte character (SBC).
Graphic Any SBC.
KanjiEBCDIC A shift-out (SO) is followed by the end of the string.
A SO is followed by MBCs, then the end of the string.
A SO is followed by SBCs, before encountering a shift-in (SI).
KanjiSJIS A SBC is encountered where we expect an MBC of 2 bytes.
KanjiEUC A SBC is encountered where we expect an MBC of 2 bytes.
A SBC, or 2 byte MBC, is encountered where we expect an MBC of 3 bytes.
Generated By: The ISF subsystem translation routines.
For Whom: End User.
Remedy: Either your SQL statement, or your data, has badly formed MBCs. Correct and resubmit.

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