Teradata SQL Error and Failure Codes from Error 6936 To 6947

SQLServerF1_Header_Small

6936 The privilege is not applicable to an external stored procedure.
Explanation: The applicable privileges are DROP PROCEDURE, ALTER EXTERNAL PROCEDURE and EXECUTE for
an external stored procedure object.
Generated By: RES module.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

6937 Authorization “%VSTR” already exists.
Explanation: The user tried to create an authorization and a table, view, trigger, macro, procedure or UDF with that
name already exists. This error occurs on the CREATE AUTHORIZATION 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.

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

6939 “%VSTR” is not an authorization.
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 authorization.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

6940 The privilege is not applicable to an Authorization.
Explanation: The applicable privileges are DROP AUTHORIZATION for an authorization object.
Generated By: RES/OPD module.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

6941 “%VSTR” is not a user logon database.
Explanation: The specified item is a database but not a User. To define a INVOKER authorization, the database must be
a user logon database. An error is resulted if the that is not the case.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

6942 “%VSTR” is neither a table function nor a table operator.
Explanation: The specified item is a table, view, macro, trigger, permanet journal, procedure, UDF and the context of the
query returning the error requires the item to be a table function or a table operator.
Generated By: SYNTAXER/RESOLVER
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

6943 Table “%VSTR” is not specified preceding table function in the FROM clause.
Explanation: table referenced in input argument of a table function must be specified preceding to table function.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the syntax and resubmit the request.

6944 UDT expression, of type %TVMID, is not compatible with %VSTR.
Explanation: A UDT expression is not compatible with either a system- defined function or operator.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Resubmit the request either not using UDTs or 1) If part of a function, ensure the UDT expression has a
implicit/explicit cast compatible with the parameter.

6945 %TVMID type argument is not compatible with %VSTR function.
Explanation: A UDT expression argument is not compatible with a parameter of a system- defined function.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Resubmit the request either not using UDTs or ensure the UDT related to the expression has a implicit/explicit
cast compatible with the parameter.

6946 UDT operand, of type %TVMID, in %VSTR operation does not have the appropriate AS ASSIGNMENT cast defined
Explanation: A UDT expression is not compatible with an operand of a system- defined operation.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Resubmit the request without UDTs or ensure the UDT related to the expression has an appropriate AS
ASSIGNMENT cast defined.

6947 Both UDT operands, in %VSTR operation, are not UDTs with the appropriate AS ASSIGNMENT cast defined.
Explanation: Both UDT expressions do not have the appropriate AS ASSIGNMENT cast defined.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Resubmit the request without UDTs or ensure the UDTs related to the expressions have an appropriate AS
ASSIGNMENT cast defined.

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