Using COPY and RESTORE After a Constraint Change - Analytics Database - Teradata Vantage

Security Administration

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-02
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantage™
Changing or deleting name:value pairs in a CONSTRAINT object after tables that contain the corresponding constraint column are archived may result in incorrect or unpredictable row level protection. Addition of new name:value pairs without changing existing constraint parameters does not have these unpredictable effects.

If the system determines that the constraint definition has a later timestamp (due to change) than the archive copy of the data used to COPY or RESTORE a row level security table, it issues the following warning:

Restored/Copied data table security may be compromised because a security constraint is inconsistent between the backup and disk. 

The COPY or RESTORE operation is allowed to complete, but security may be compromised.

Make sure you understand the possible security effects before you COPY or RESTORE a row level security table.