Security Configurations for Migration | Teradata Vantage - Security Configurations - Analytics Database - Teradata Vantage

Teradata Vantageā„¢ - Analytics Database Node Software Migration Guide - 17.20

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-01-27
dita:mapPath
ydx1628095838609.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-5942
Product Category
Teradata Vantage
If you have created a custom security configuration for the source system by editing the default TdgssUserConfigFile.xml file, the configuration is not automatically migrated to the new destination system. After migrating data to the freshly installed Analytics Database on the destination system, only the new default security configuration is available. To transfer a custom security configuration to the new destination system, you must complete the following steps:
  1. Save the edited TdgssUserConfigFile.xml file from the source system. This file is located in the following directory on the Control Node: /opt/teradata/tdat/tdgss/site
  2. Replace the TdgssUserConfigFile.xml file on the destination system with the one saved from the source system.
  3. Activate the custom configuration on the destination system.

Row-level security is part of the Mandatory Access Control (MAC) feature. If row level security is applied in the source system, you must restore database SYSLIB before you restore any user data on the target system. You must also restore SYSLIB a second time after the migration of the user data is complete.

Prior to copying row level security tables, re-associate each copied constraint with its respective constraint function.

After the migration, refer to Teradata Vantageā„¢ - Analytics Database Security Administration, B035-1100, to plan and implement your new security features.