Teradata SQL Error and Failure Codes from Error 5755 To 5768

5755 The number of table reference and alias names do not correspond.
Explanation: The Merge-Into statement did not provide a corresponding number of table reference and alias names.
Generated By: Syn module.
For Whom: End User.
Remedy: Re-submit the query with an equal amount of table reference and alias names.

5756 The table reference must be a using descriptor list or SELECT statement.
Explanation: The table reference of a Merge-Into statement was used improperly.
Generated By: Syn module.
For Whom: End User.
Remedy: Re-submit the query with a table reference that is either a using descriptor list or SELECT statement.

5758 The search condition must fully specify the Target table primary index and partition column(s) and expression must match INSERT specification primary index and partition column(s).
Explanation: The search condition must fully specify an equality constraint on the primary index and partition column(
s) between the source and target table. Other set of conditions must be ANDed with primary index and partition column
conditions. If an expression/column is selected for the target primary index in the INSERT part of the MERGE
statement, that expression must be matched with the target primary index on the ON clause. Expression should also not
involve a non-deterministic UDF/UDM or RANDOM function
Generated By: Parser.
For Whom: End User.
Remedy: Correct the MERGE statement and resubmit.

5759 The Merge-Into match condition cannot reference a table that is neither a target nor source table.
Explanation: A Merge-Into match condition cannot reference a table that is neither the target nor source table.
Generated By: Opt module.
For Whom: End User.
Remedy: Re-submit the Merge-Into query with a match condition that does not reference any table besides the target or
source table.

5760 The SELECT subquery from the table reference must fully specify either a UPI value or else a USI value.
Explanation: The SELECT subquery from the table reference must either specify a Unique Primary Index or Unique Secondary
Index. OR The SELECT subqury in the Merge-Into statement contains a SELECT AND CONSUME statement.
*DR86975-mkw-01*
Generated By: Opt module.
For Whom: End User.
Remedy: Re-submit the Merge-Into statement with a Select subquery in the table reference that contains either a UPI
value or USI value. If SELECT AND CONSUME statemnt is used in the Select subquery, we will need to correct the query.

5761 The Merge-Into statement cannot be a triggered action.
Explanation: A Merge-Into statement cannot be a triggered action.
Generated By: Res module.
For Whom: End User.
Remedy: Remove any triggers that contains a Merge-Into statement as a triggered action.

5764 String functions like INDEX and TRIM are not allowed on LOBs.
Explanation: String functions like INDEX and TRIM are not allowed on LOBs.
Generated By: OPT modules (optwexp).
For Whom: End User.
Remedy: Cast the LOB as a VARBYTE or VARCHAR.

5765 The LOB datatpye is not allowed to be returned in the DatInfo parcel.
Explanation: The LOB datatpye is not allowed to be returned in the DatInfo parcel as part of the response to a Prepare
(’S’ in the Options parcel).
Generated By: Res modules (resbspl).
For Whom: End User.
Remedy: Change the response mode to MultipartRecord and a DataInfoX parcel will be returned.

5766 The Locator is invalid because the response spool has been dropped.
Explanation: The Locator referenced in the SQL statement is not valid because the response spool which generated the
locator has been dropped.
Generated By: Dis modules (DisLocValid).
For Whom: End User.
Remedy: Set KeepResp to ’Y’ and resubmit the select to create the locator.

5767 The Locator is invalid because this request is in a different transaction.
Explanation: The Locator referenced in the SQL statement is not valid because the Select to fetch the LOB is in a different
transaction then the Select that created the locator.
Generated By: Dis modules (DisLocValid).
For Whom: End User.
Remedy: Keep both Selects in the same transaction or create a static Locator (LobSelect = ’S’ in the Options parcel).

5768 The Locator is invalid because it has been changed.
Explanation: The Locator referenced in the SQL statement is not valid because it has been changed since it was created.
Generated By: Dis modules (DisLocValid).
For Whom: End User.
Remedy: Don’t modify the locator before returning it to the server.

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