Teradata SQL Error and Failure Codes from Error 6926 To 6935

SQLServerF1_Header_Small

6926 WITH [RECURSIVE] clause or recursive view is not supported within WITH [RECURSIVE] definitions, views, triggers or stored procedures.
Explanation: A WITH clause or a recursive view is being used inside a WITH definition, view, or stored procedure.
Generated By: SYN/OPT modules
For Whom: End User
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the recursive query rules and resubmit the request.

6927 Illegal or unsupported use of TOP N inside the recursive query/view.
Explanation: There is a TOP N operation being performed inside the recursive query/view definition, which is not
allowed.
Generated By: SYN/OPT modules
For Whom: End User
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the recursive query rules and resubmit the request.

6928 Recursive queries must begin with at least one non-recursive SELECT.
Explanation: The first SELECT of recursive query/view’s body must not contain a recursive reference.
Generated By: RES modules
For Whom: End User
Remedy: Examine the SQL statement and verify that the request is correct. If there is already a non-recursive SELECT in
the body of the query/view, move that SELECT to the top of the set operation. If not, then rewrite the statement to adhere
to the recursive query rules and resubmit the request.

6929 Objects referenced in a recursive query/view may not have aliases whose name match the recursive name or its aliases.
Explanation: Objects referenced in a recursive query/view may not have alias names that are the same as the recursive
query/view name or any of its aliases.
Generated By: RES modules
For Whom: End User
Remedy: Examine the SQL statement and verify that the request is correct. Replace the conflicting alias names with a different
name, and resubmit the request.

6930 Overlapping recursive object aliases are not allowed.
Explanation: An alias for a recursive object has been defined within the scope of another recursive object alias. This is not supported.
Generated By: RES modules
For Whom: End User
Remedy: Examine the SQL statement and verify that the request is correct. Remove the conflicting alias, and resubmit
the request.

6931 WITH CHECK OPTION is not allowed for recursive views.
Explanation: WITH CHECK OPTION is being used while creating a recursive view, which is not allowed.
Generated By: RES modules
For Whom: End User
Remedy: Examine the SQL statement and verify that the request is correct. Remove the WITH CHECK OPTION from
the request and resubmit it.

6932 Multiple WITH definitions are not supported.
Explanation: Multiple WITH definitions are not currently supported.
Generated By: SYN modules
For Whom: End User
Remedy: Examine the SQL statement and verify that the request is correct. Remove one or more WITH definition from
the WITH definition list and resubmit the request. A non-recursive WITH definition may be defined equivalently as
derived tables within the main query.

6933 External Stored Procedure “%VSTR” already exists.
Explanation: The user tried to create an external stored procedure and a table, view, trigger, macro, procedure, UDF or
authorization with that name already exists. This error occurs on the CREATE (EXTERNAL) PROCEDURE statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Examine the statement and verify that the request is correct. Change the statement to specify a different name
and resubmit the request.

6934 External Stored Procedure “%VSTR” does not exist.
Explanation: The user referenced an external stored procedure that does not exist in the database.
Generated By: RES/OPD modules.
For Whom: End User.
Remedy: Check the spelling of the external stored procedure. Check for the correct database name. Correct the request
and resubmit it.

6935 “%VSTR” is not an external stored procedure.
Explanation: The specified item is a table, view, macro, trigger, permanet journal, procedure, or UDF and the context of the query returning the error requires the item to be an external stored procedure.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

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