Teradata SQL Error and Failure Codes from Error 6879 To 6901

6879 The name %VSTR does not match an existing name.
Explanation: –The Transform Group Name specified in a REPLACE TRANSFORM statement does not match the existing
Transform Group name.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct and re-submit the query.

6880 Invalid UDT Cast. %VSTR.
Explanation: The Cast is invalid due to one of the following reasons: –Cast between Internal UDT and other types of
UDT is not allowed
Generated By: RES modules.
For Whom: End User.
Remedy: Correct and re-submit the query.

6881 Error: %VSTR.
Explanation: The request contains an error. ’%VSTR’ identifies the specific error condition.
Generated By: RES modules.
For Whom: End User.
Notes: This is a generic error generated by the Parser. The ’%VSTR’ needs to be filled out with the proper message concerning
the error encountered in the Parser.
Remedy: Correct the error and resubmit the request.

6882 UDT has no methods
Explanation: This UDT has no methods defined for it.
Generated By: Resolver Modules
For Whom: End User
Remedy: Verify that the request is correct and resubmit.

6883 Cannot specify both Protected and Compile options for UDT Ordering or Transform routine %FSTR.
Explanation: If a User Defined Function(UDF) or User Defined Method(UDM) is an Ordering or Transform routine for a
User Defined Type(UDT), the ALTER FUNCTION/METHOD command cannot specify both the PROTECTED optioin and
the COMPILE option for the UDF/UDM in one single command.
Generated By: OPD Alter UDF module
For Whom: End User
Remedy: Submit the request in two ALTER FUNCTION/METHOD commands. E.g. Alter Function MyFunc execute
Protected; Alter Function MyFunc compile;

6884 Failed to compile the Constructor Function for UDT %FSTR
Explanation: The compilation of the auto-generated Constructor function for the User Defined Type(UDT) failed.
Generated By: OPD modules
For Whom: System
Notes: This is not a User error.
Remedy: Contact your support representative.

6885 Alter Method not supported on FastPath/Auto-generated UDM
Explanation: Fastpath or auto-generated UDMs may not be altered/compiled.
Generated By: Resolver Modules
For Whom: End User
Remedy: Verify that the request is correct and resubmit.

6886 Reference to UDT/UDM ’%VSTR’ is not allowed in this context.
Explanation: This error occurs in either of the following situations: 1. The user tried to insert rows into a UDT/UDM,
which is not allowed. 2. The specified item is a UDT/UDM, but the context of query returning the error requires the item to be a table,view.
Generated By: Resolver Modules
For Whom: End User
Remedy: Correct the statement and resubmit the request.

6899 FallBackSetting is %VSTR – NO FALLBACK is not allowed on %FSTR.
Explanation: The NO FALLBACK option is not allowed when DBSControl field FallBackSetting is set to ALWAYS
FALLBACK.
Generated By: Resolver.
For Whom: End User.
Remedy: Do not specify the NO FALLBACK option unless the DBSControl field FallBackSetting is reset to another
value.

6900 FallBackSetting is %VSTR – %FSTR is set to FALLBACK.
Explanation: This is a warning message. The NO FALLBACK option is not allowed when DBSControl field FallBackSetting
is set to ALWAYS FALLBACK. The database object in question will be converted to FALLBACK.
Generated By: Resolver.
For Whom: End User.
Remedy: None. User has to be aware that the database object specified in the command is set to FALLBACK.

6901 Only LATIN and UNICODE are valid CLOB server character sets.
Explanation: LATIN and UNICODE are the only valid server character sets for CLOBs.
Generated By: Resolver
For Whom: End User.
Remedy: Specify a character set of LATIN or UNICODE

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