Using COPY or RESTORE to Migrate the Row Level Security Setup to Another System - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ied1556235912841.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1100
lifecycle
previous
Product Category
Teradata Vantageā„¢

When migrating the RLS setup from one system to another, a COPY of the SYSLIB database containing all the constraint UDFs automatically re-assigns new internal function IDs to the UDFs on the target system. These re-assigned IDs no longer match the IDs stored in DBC.ConstraintFunctions copied over to the target system during the migration.

Prior to migrating RLS tables to the target system, you must re-assign the UDFs in each constraint on the target system, using the procedures in Altering or Dropping CONSTRAINT Objects, as follows:

  1. Use ALTER CONSTRAINT to drop all UDFs from each constraint.
  2. Use ALTER CONSTRAINT to re-specify the UDFs in the CONSTRAINT object. The ALTER CONSTRAINT statement then inserts the corresponding rows in DBC.ConstraintFunctions with the newly assigned function ids.