Teradata SQL Error and Failure Codes from Error 5769 To 5784

SQLServerF1_Header_Small

5769 The Locator is invalid due to an internal error.
Explanation: The Locator referenced in the SQL statement is not valid due to an internal error.
Generated By: Dis modules (DisLocValid).
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

5770 %VSTR is not allowed on UDT column.
Explanation: UDT column can not have these attributes: compress, default, constraint,…
Generated By: Syntaxer, OPU and OPD modules.
For Whom: End User.
Remedy: Remove UDT column in the query, or rewrite the statement without using the prohibited attribute.

5771 Index not supported by UDT ’%TVMID’. %VSTR
Explanation: Indexing is not supported by this UDT.
Generated By: Optimizer, GNS and GNC modules.
For Whom: End User.
Remedy: Rewrite the statement without using indexing on this UDT.

5772 Foreign Key is not allowed on UDT columns.
Explanation: A UDT column is not allowed to be a foreign key.
Generated By: OPU modules.
For Whom: End User.
Remedy: Rewrite the statement without listing UDT column as the foreign key.

5774 Invalid data type for Identity Column %VSTR.
Explanation: An identity column may only be of an exact numeric data type. Valid data types are BYTEINT, SMALLINT,
INTEGER, DECIMAL(n,0) and NUMERIC(n, 0).
Generated By: SYN module.
For Whom: End User.
Remedy: Modify the CREATE TABLE or ALTER TABLE statement with a valid data type for the identity column and resubmit
the request.

5776 The GENERATED ALWAYS Identity Column %VSTR may not be updated.
Explanation: User attempted to update a value of a GENERATED ALWAYS identity column.
Generated By: OPT module.
For Whom: End User.
Remedy: Modify the UPDATE statement accordingly and re-submit the request.

5778 A response buffer of at least 65,000 bytes is needed for a high-performance transfer.
Explanation: A response buffer of at least 65,000 bytes is needed for a high-performance LOB transfer. The query
(SELECT ?) with a Locator passed in is usually used for a high performance LOB transfer. The query must also be sent in
with MultipartRecord as the response mode.
Generated By: Optimizer modules (OptRet).
For Whom: End user
Remedy: Make the response mode MultipartRecord and the response buffer at least 65,000 bytes.

5780 Cannot DROP a user or database that has DBQL enabled.
Explanation: The user tried to drop a user or database which has rule(s) in the DBQLRules table.
Generated By: OPD modules.
For Whom: The DBA and the End User.
Remedy: Submit END QUERY LOGGING for the all DBQL rules for the user, as shown by SEL * FROM DBC.DBQLRULES.
Resubmit the DROP USER request.

5781 You cannot collect statistics on more than 32 groups of non-indexed columns.
Explanation: Multiple column statistics are stored as “psuedo” indexes within DBC.Indexes and related internal structures.
These structures have limits regarding the total number of indexes for a table and the number of columns within an
index. As a result, there is a limit on the number of multiple column statistics that can exist for a given table.
Generated By: OPD modules.
For Whom: End User.
Remedy: Drop any unused statistics on multiple non-indexed columns for the specified table.

5782 Non-Indexed statistics already exist on the specified set of indexed fields.
Explanation: Statistics were previously collected on the set of columns comprising this index. At the time of this previous
collection, the set of columns were not indexed. The existing statistics should be dropped using the COLUMN list syntax
and then statistics can be collected on this index.
Generated By: OPD modules.
For Whom: End User.
Remedy: Drop the statistics defined on the set of non-indexed fields.

5783 DBQL Rule Count has become negative.
Explanation: The user tried to END QUERY LOGGING and the dictionary table DBC.DBQLRULECOUNTTBL will
have a negative number of rules.
Generated By: OPD modules.
For Whom: Internal only.
Remedy: The processing of BEGIN and END QUERY LOGGING has been interrupted or failed, and the number of rules
in the DBQLRULETBL is not the same as the value in the DBQLRULECOUNTTBL. Administrator may replace the value
manually by disabling accessrights.

5784 Illegal usage of Identity Column %VSTR.
Explanation: User attempted to define an invalid identity column or use an identity column incorrectly. The error is
returned if: 1) an identity column is defined as a) part of a composite index b) a join index or hash index c) a primary partition
index d) a value-ordered index. 2) the input parameter of an INSERT into identity column is a using field (e.g., :F1)which is part of an expression, e.g. :F1+:F2 or :F1+2. 3) an identity column is defined in a temporary or volatile table. It may
only be defined in a permanent table. 4) a USING statement contains multiple INSERT statements that insert into different
identity column tables. 5) the input parameter of an INSERT into identity column of type BY DEFAULT is a using field
(e.g., :F1) that is being reused in another parameter in the insert statement, e.g. USING(F1 INT, F2 INT) INS tab(:F1,:F1);
Generated By: SYN, RES, OPT modules.
For Whom: End User.
Remedy: Modify the statement accordingly and re-submit the request.

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