Teradata SQL Error and Failure Codes from Error 6902 To 6915

SQLServerF1_Header_Small

6902 User-defined %FSTR Transform is not defined for UDT ’%TVMID’ %VSTR.
Explanation: A Transform Group Name and UDT Identifier combination is not found in DBC.UDTTRANSFORM dictionary
table..
Generated By: Syntaxer/Resolver and Optimizer Modules
For Whom: End User
Remedy: Add a definition of the UDT-GroupName to the DBC.UDTTRANSFORM dictionary table.

6903 The source data type of the User-defined Transform should be a %VSTR.
Explanation: The source data type of a ToSQL transform should be a Pre-defined Base Type whereas a FromSQL transform
should be a UDT.
Generated By: Syntaxer/Resolver and Optimizer Modules
For Whom: Internal
Remedy: Probably the wrong Par node was created.

6904 The target data type of the User-defined Transform should be a %VSTR.
Explanation: The target data type of a FromSQL transform should be a Pre-defined Base Type whereas a ToSQL transform
should be a UDT.
Generated By: Syntaxer/Resolver and Optimizer Modules
For Whom: Internal
Remedy: Use the auto-generated implicitly assignable user-defined CAST.

6906 Iterated request: Disallowed statement type (%VSTR).
Explanation: Non-DML and some DML statements are not allowed with an iterated request.
Generated By: SYN, RES modules.
For Whom: End User.
Remedy: Resubmit the statement via a non-iterated request.

6907 Iterated request: USING field or parameter reference required.
Explanation: The statement in the request does not reference any using field. Or a request with no parameter markers is
not allowed to be iterated in V2R6 implementation of Array Support feature.
Generated By: RES modules.
For Whom: End User.
Remedy: Resubmit the statement via a non-iterated request, or modify the statement to reference using field/parameter
correctly.

6908 Iterated request: Multi-statement requests not supported.
Explanation: Multi-statement requests are not supported with an iterated request.
Generated By: SYN modules.
For Whom: End User.
Remedy: Either submit the multi-statement request with only one using row OR submit a single statement request with
multiple using data rows.

6910 UDT ’%FSTR’ is a Distinct type, which can not be initialized through a NEW specification.
Explanation: The New specification is used to initialize instantiable UDTs. Distinct types are not instantiable.
Generated By: Syntaxer/Resolver Modules
For Whom: End User
Remedy: Use the auto-generated implicitly assignable user-defined CAST.

6911 The body for Method ’%FSTR’, of UDT ’%TVMID’, is not defined.
Explanation: The method being invoked is defined to be external, but the body does not exist.
Generated By: Syntaxer/Resolver Modules
For Whom: Internal
Remedy: The User should define a body for the method using CREATE METHOD.

6912 A triggered stored procedure can not contain OUT or INOUT parameters or dynamic result sets.
Explanation: A stored procedure called from a trigger can not contain OUT or INOUT parameters or return dynamic
result sets.
Generated By: Optimizer
For Whom: End User.
Remedy: Make all the parameters IN parameters.

6913 A triggered stored procedure can not contain DDL.
Explanation: A stored procedure called from a trigger can not contain DDL, DCL, or transaction control statements.
Generated By: Resolver
For Whom: End User.
Remedy: Remove DDL, DCL, and transaction control statements.

6914 SAMPLE clause not allowed with ROLLUP, CUBE, or GROUPING SETS.
Explanation: Sample Clause is not supported with group by operators Rollup, Cube, or Grouping Sets.
Generated By: OptLgSmp
For Whom: End User.
Remedy: None.

6915 Invalid Top N Value: %VSTR.
Explanation: This error is produced when the value of N in the TOP N feature is invalid. This includes : 1. Zero or negative
N 2. N exceeds the maximum decimal value 3. N > 100 and the percent option is specified. 4. N is a decimal value and
the percent option is not specified.
Generated By: SYN and RES modules
For Whom: End users.
Remedy: Use a valid value of N.

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