Teradata Database Message 5321 - 5321 - Analytics Database - Teradata Vantage

Analytics Database Messages

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
15.xx,16.xx,17.xx
Published
June 2022
ft:locale
en-US
ft:lastEdition
2023-01-05
dita:mapPath
sfx1628096178347.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-1096
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.