Teradata SQL Error and Failure Codes from Error 5982 To 5997

SQLServerF1_Header_Small

5982 Error table for LOGGING ERRORS cannot be part of a replication group.
Explanation: The user tried to add an error table to a replication group.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

5983 LOGGING ERRORS option may not be used while error table %VSTR has secondary indexes.
Explanation: The user specified LOGGING ERRORS for an INSERT-SELECT or MERGE-INTO request whose target
table has secondary indexes defined on it error table.
Generated By: RES module.
For Whom: End User.
Remedy: Drop all secondary indexes on the error table and re-submit the request.

5984 Table structure or primary index may not be altered while its error table exists.
Explanation: The user tried to add or drop a column from a data table, or alter its primary index column(s) when an
error table has been defined for the table. Altering the partitioning of a data table’s partitioned primary index is permitted.
Generated By: RES module.
For Whom: End User.
Remedy: Drop the error table and re-submit the request

5985 ALTER TABLE is disallowed on error table %VSTR.
Explanation: The user submitted an ALTER TABLE on an error table.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

5986 Expanded request size of a replication DDL statement exceeds parser limit of 1048500 bytes.
Explanation: The user specified a request that exceeds the specified limit.
Generated By: OPURSSQL
For Whom: End user
Remedy: The expanded request size for a DDL replication in bytes exceeds the limit imposed by the system. Check the
request, correct and re-submit.

5991 Error during resolver or plan generation – try again.
Explanation: This is a retryable error code. Parser encountered an error while generating the plan for a request with
USING values. OR Parser encountered conflicts arised from concurrent accesses to DBC tables during resolver phase.
Generated By: OPT or RES modules.
For Whom: This is an internal error that should be handled by other procedures. It should not cause a crash or be
reported to a user..
Remedy: Resubmit the request.

5992 A syntax error was found in the QUERY_BAND.
Explanation: The format of the Query_Band is incorrect. The syntax of each pair should be name=value;.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct and re-submit the statement.

5993 The QUERY_BAND exceeds the maximum length.
Explanation: The Query_Band exceeds the maximum length allowed.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct and re-submit the statement.

5994 A QUERY_BAND name exceeds the maximum length.
Explanation: A name in the Query_Band exceeds the maximum length allowed.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct and re-submit the statement.

5995 A QUERY_BAND value exceeds the maximum length.
Explanation: A value in the Query_Band exceeds the maximum length allowed.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct and re-submit the statement.

5996 A duplicate name was found in the QUERY_BAND.
Explanation: Each name in the Query_Band must be unique.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct and re-submit the statement.

5997 SET QUERY_BAND for TRANSACTION must be the first statement in a multi-statement request.
Explanation: The Set QUERY_BAND for TRANSACTION statement must be the first statement in a multi_statement
request.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct and re-submit the statement.

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