Teradata SQL Error and Failure Codes from Error 5892 To 5901

SQLServerF1_Header_Small

5892 An invalid statement was performed on a Queue Table.
Explanation: A particular statement may not be performed on a queue table. The following statements are not allowed
for queue tables: – CREATE/REPLACE TRIGGER, – CREATE/REPLACE VIEW, – CREATE/ALTER REPLICATION
GROUP, – CREATE/DROP HASH INDEX, – CREATE/DROP JOIN INDEX, – CREATE INDEX used to create a USI on the
QITS column.
Generated By: Resolver modules.
For Whom: End User.
Remedy: Remove the invalid statement.

5893 An invalid option for SELECT AND CONSUME TOP was supplied.
Explanation: The SELECT AND CONSUME TOP clause contains one of the following options that are not valid. – The
PERCENT option exists, – The WITH TIES option exists, – The integer value is other than one.
Generated By: Syntaxer modules.
For Whom: End User.
Remedy: Remove the invalid option from the SELECT AND CONSUME TOP clause and resubmit the SELECT statement.

5894 The SELECT AND CONSUME statement is not referencing a queue table.
Explanation: The table in the SELECT AND CONSUME statement is not a queue table.
Generated By: RES modules.
For Whom: End User.
Remedy: Change the statement to reference a queue table.

5895 A function, operator, or expression involving the SELECT AND CONSUME statement is invalid.
Explanation: A function, operator, or expression involving the SELECT AND CONSUME statement is invalid for one of
the following reasons: – an aggregate (e.g., SUM, COUNT) function is specified, – an ordered analytical function is specified,
– a UNION set operator is specified, – a MINUS/EXCEPT operator is specified, – a INTERSECT operator is specified.
Generated By: Resolver modules.
For Whom: End User.
Remedy: Remove the invalid expression from the SELECT AND CONSUME statement and resubmit the statement.

5896 Multiple SELECT AND CONSUME statements in a request is not allowed.
Explanation: The multi-statement request contains more than one SELECT AND CONSUME or INSERT … SELECT
AND CONSUME statements. This is not allowed even if the statements reference different queue tables.
Generated By: RES modules.
For Whom: End User.
Remedy: Split the request into multiple requests.

5897 The utility does not support queue tables.
Explanation: FastLoad, MultiLoad, and FastExport utilities do not support queue tables. The Teradata Warehouse
Builder Load, Update, and Export Operators are also not supported.
Generated By: RES modules.
For Whom: End User.
Remedy: Load, or unload, the table with SQL statements.

5898 An updatable cursor is not allowed on select and consume.
Explanation: Teradata does not allow updatable cursor on Select and Consume statement.
Generated By: Res modules.
For Whom: End User.
Remedy: Do not use updatable cursor on Select and Consume.

5899 A queue table may not be referenced.
Explanation: The CREATE TABLE or ALTER TABLE statement contains a REFERENCES clause for a queue table.
Generated By: Syntaxer modules.
For Whom: End User.
Remedy: Remove the invalid option from the CREATE TABLE or ALTER TABLE statement.

5900 A replication group already exists with that name.
Explanation: Replication group names must by unique.
Generated By: RES or OPD module.
For Whom: End User.
Remedy: Specify a unique replication group name and re-submit the request.

5901 Replication Group ’%VSTR’ does not exist.
Explanation: The user referred to a replication group as %VSTR. That replication group does not exist.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the Teradata SQL statemenet by using a valid name for the replication group and resubmit the request.

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