Teradata Database Message 5321 - 5321 - 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
Constraint, primary index, or secondary index with the same name "%VSTR" already exists in table.
Explanation
The constraint, primary index, or secondary index name must be unique in a table regardless of constraint type. This error can also be returned by post restore script processing if the system journal index has different name in dump than in the target system, this case can be ignored as it is not a problem.
Generated By
RES and OPT modules.
For Whom
End User.
Notes
Names of join indexes and hash indexes must be unique within a database. For example, a join index must not have the same name as a table in the same database but it may have the same name as a constraint, primary index, or secondary index as in a table on which the join index is defined.
Remedy
Give the constraint or index a different name and resubmit the request.