Teradata SQL Error and Failure Codes from Error 6835 To 6846

6835 Method “%VSTR” already exists.
Explanation: This error is displayed when tried to create method which is already exist in system.
Generated By: Syntaxer/Resolver, Optimizer
For Whom: End User
Remedy: Examine the Teradata SQL statement and verify that the request is correct. Change the statement to specify a
different name and resubmit the request.

6836 %FSTR does not have %VSTR access to SYSUDTLIB database.
Explanation: The user does not have the proper access rights to execute this request. This statement is authorized for: a)
DBC, b) any user granted the USAGE privilige.
Generated By: RES and OPT modules.
For Whom: End User.

6837 “%VSTR” is not a Type.
Explanation: The specified item is not a User Defined Type. In the context of query, User Defined Type is expected.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

6838 “%VSTR” is not a Method.
Explanation: The specified item is not a User Defined Method. In the context of query, User Defined Method is expected.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

6839 “%VSTR” operation on “%FSTR” not allowed: Referenced by other object(s).
Explanation: Replace/Rename/Drop operation is allowed only when the database object affected by the operation is
not referenced by any other database object(s). For instance, a DROP FUNCTION operation will abort if the Function being
dropped is the Ordering routine for a UDT.
Generated By: OPD module.
For Whom: End User.
Remedy: Remove dependency by modifying or dropping dependent object and then re-try the query.

6840 Database “%VSTR” cannot be deleted: object(s) in other database depending on object(s) in this database.
Explanation: Database cannot be deleted because objects in some other database depends on objects in this database. Ex:
UDT1 exists sysudtlib database and it uses db1.udf1 as cast routine. In that case delete database db1 will be not allowed as
sysudtlib.udt1 depending on db1.udf1.
Generated By: OPD module.
For Whom: End User.
Remedy: Remove dependency by modifying or dropping dependent object and then run delete database.

6841 Database should be SYSUDTLIB.
Explanation: The database in which a type can be created or an existing UDT to be accessed need to be SYSUDTLIB.
Generated By: RES modules.
For Whom: End User.
Remedy: Create the type in SYSUDTLIB database. While accessing an existing UDT , ensure that the Database name is
SYSUDTLIB. Correct the request and resubmit the query.

6842 Attribute type cannot be the type under creation or being altered.
Explanation: The UDT under creation (CREATE TYPE) or being altered (ALTER TYPE) is not allowed to be declared as
the data type of an attribute.
Generated By: RES modules.
For Whom: End User
Remedy: Resubmit the query with a different type for the attribute.

6843 Invalid field attribute specified for a method parameter.
Explanation: When creating or replacing a method, a user can only specify the character type and nullable property for
a method parameter. Any other field attributes specified will result in an error.
Generated By: RES modules.
For Whom: End User
Remedy: Correct the statement and resubmit the request.

6844 A method/function already exists in the database with the same name and parameter data types.
Explanation: The user tried to create or replace a method or provide the specification for the method in the create type
statement, which has the same overloaded method name and parameter data types with an existing method/function in
the database.
Generated By: RES modules.
For Whom: End User
Remedy: Correct the statement and resubmit the request.

6846 LOCAL is allowed only on Internal Type. %VSTR
Explanation: The LOCAL key word, which signifies the “fast-path”, is only allowed on the Teradata Internal User
Defined Type. It is not allowed on the Distinct or Structured types.
If both Source and Target data types specified for a Cast are not Internal UDT type, the Cast routine must not be LOCAL.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the query.

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