Teradata Database Message 5562 - 5562 - Analytics Database - Teradata Vantage

Teradata® VantageCloud Lake - Analytics Database Messages

Edition
Lake
Product
Analytics Database
Teradata Vantage
Published
October 2022
Language
English (United States)
Last Update
2024-02-26
dita:mapPath
tzr1629746512312.ditamap
dita:ditavalPath
ft:empty
dita:id
vza1585613049811
lifecycle
latest
Product Category
Teradata® Vantage™
Message
The UPDATE part of the UPSERT statement is not a single-AMP operation.
Explanation
The UPDATE part of the UPSERT statement is not a single-AMP operation, this could be due to one or more of the following reasons: 1. The user did not fully specify the primary index in the UPDATE part of the UPSERT statement. The same fully specified primary index must be used on both the UPDATE and INSERT parts of an UPSERT statement, since the purpose of an UPSERT is to find a row or rows to update, and if no row is found to insert a corresponding row into the table. 2. The WHERE clause of the UPDATE part of the UPSERT statement compares the fully specified primary index against another field of the same table. This results in an all-AMP update. 3. The WHERE clause of the UPDATE part of the UPSERT statement compares the fully specified primary index against some value using a non-equality constraint. This also results in an all-AMP update. 4. The WHERE clause of the UPDATE part of the UPSERT statement compares the fully specified primary index with an operand of a different data type. This could cause the system to convert the primary index values to match the data type of the operand and thus result in an all-AMP update.
Generated By
Parser.
For Whom
End User.
Notes
None
Remedy
Correct the UPSERT statement and resubmit.