Teradata SQL Error and Failure Codes from Error 5971 To 5981

SQLServerF1_Header_Small

5971 LOGGING ERRORS is not applicable to MERGE-INTO with unreasonable updates or inserts.
Explanation: The user specified LOGGING ERRORS for a MERGE-INTO request in which the update or insert rows
have to be re-distributed prior to the row merge operation. This error is returned when the primary index value is being updated, or when PI values for the insert may be different from the PI value specified in the ON clause.
Generated By: RES module.
For Whom: End User.
Remedy: Remove the LOGGING clause and re-submit the request.

5972 LOGGING ERRORS is applicable to permanent data tables only.
Explanation: The user specified LOGGING ERRORS for a table that is not a permanent data table.
Generated By: RES module.
For Whom: End User.
Remedy: Specify LOGGING ERRORS for permanent data tables only.

5973 Error limit is out of range, valid range is 1 to 16,000,000.
Explanation: The user specified an out-of-range error limit.
Generated By: RES module.
For Whom: End User.
Remedy: Specify an error limit of 16,000,000 or less and re-submit the request.

5974 Multi-statement request with LOGGING ERRORS is not allowed.
Explanation: The user specified LOGGING ERRORS for one or more statements in a multi-statement request.
Generated By: RES module.
For Whom: End User.
Remedy: Re-submit statement with LOGGING ERRORS as a single statement request.

5975 Creator ’%VSTR’ of the stored procedure ’%FSTR’ does not exist.
Explanation: A Dynamic SQL statement from stored procedure needs creator to exist during stored procedure execution,
for access right verification. This error is reported when creator does not exist.
Generated By: RES modules.
For Whom: End User.
Remedy: Ensure that the creator of the stored procedure is present and resubmit the call statement.

5976 The LOGGING ERRORS feature is disabled.
Explanation: The user specified LOGGING ERRORS when the feature is disabled through the internal Dbscontrol flag,
NoErrorHandling.
Generated By: RES module.
For Whom: End User.
Remedy: Re-submit the statement without the LOGGING ERRORS clause.

5977 Invalid MERGE-INTO statement: %VSTR
Explanation: The user specified a MERGE-INTO statement that violated one of the following Teradata exceptions to Full
ANSI MERGE standards:
a) The <search condition> following the ON keyword must specify an equality constraint on the primary index of the target table. The specified primary index value must match the primary index value implied by the column values specified
in the INSERT clause. If the PI value is the result of an expression, the expression cannot reference any column in the target table. Additionally, the <search condition> may not contain subqueries or references to columns that do not belong to
either the source or target table. If the target table is a PPI table, the values of the partitioning columns must also be specified in the <search condition>, and the INSERT clause must specify the same partitioning column values as the <search
condition>.
b) UPDATEs of the primary index column(s) are not supported. For PPI tables, this restriction is further extended to not supporting UPDATEs on partitioning column(s) as well.
c) PI of Target table cannot be an identity column d) MergeInto is not allowed on Unhashed table
Generated By: Parser.
For Whom: End User.
Remedy: Correct the statement and re-submit the request.

5978 Error table already exists for %VSTR.
Explanation: The user tried to create an error table for a data table which already has an error table.
Generated By: RES module.
For Whom: End User.
Remedy: There is no need to re-submit the request as an error table has already been defined for the data table.

5979 An error table may be defined for a permanent data table only.
Explanation: The user tried to create an error table for another error table, or for a non-permanent data table.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

5980 Error table does not exist.
Explanation: An error table must exist before an INSERT-SELECT or MERGE-INTO with LOGGING or a
SHOW/HELP/DROP ERROR TABLE FOR <table> request is valid.
Generated By: RES module.
For Whom: End User.
Remedy: Create an error table before re-submitting the request.

5981 Triggers, join indexes, and hash indexes may not be defined on error table %VSTR.
Explanation: The user tried to create a trigger, join index, or hash index on an error table.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

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