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 Teradata 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:
- Save the edited TdgssUserConfigFile.xml file from the source system.
- Replace the TdgssUserConfigFile.xml file on the destination system with the one saved from the source system.
- Activate the custom configuration on the destination system.
If row level security is applied in the source system, SYSLIB has to be archived and restored before and after migration procedures.
Prior to copying row level security tables, re-associate each copied constraint with its respective constraint function.
After the migration, refer to Security Administration, B035-1100 to plan and implement your new security features. This document is available from http://www.info.teradata.com.