Configure Teradata Data Lab for High Availability | Teradata Viewpoint - 17.10 - Configuring Teradata Data Lab for High Availability - Teradata Viewpoint

Teradata® Viewpoint Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Viewpoint
Release Number
17.10
Release Date
October 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-2207-101K
Language
English (United States)
Teradata Data Lab can be configured to use Unity's high availability capabilities so that users can continue to work with their labs even if one of their Teradata systems is unavailable.
  1. Transfer data, including lab group users, lab databases, and lab group roles, from the preexisting Teradata systems to Teradata systems managed by the Unity cluster.
  2. From the Monitored Systems portlet, do the following:
    1. Verify that both the preexisting and new Unity-managed Teradata systems are present in the Monitored Systems portlet.
    2. Verify that both systems are enabled.
    3. Verify that the Dictionary collector is enabled for both systems.
  3. Type the following command to shut down the DCS from the active cache database server:
    /etc/init.d/dcs stop
  4. Run the dcsadmin command from the active cache database server:
    /opt/teradata/viewpoint/dcs/bin/dcsadmin.sh
  5. Type help to verify the migratedatalabssystem command is available.
  6. Run the migratedatalabssystem command.
  7. Select a source system (original system).
  8. Select a target system (new Unity-managed Teradata system).
  9. Verify that output to make sure the migration was successful.
  10. Type the following command to start the DCS from the active cache database server:
    /etc/init.d/dcs start
    The migration is ready to be validated.
  11. From the Data Labs portlet, make sure the migration completed successfully by doing the following:
    1. Verify the new Unity-managed Teradata systems have all the data labs data that was on the original systems. Also verify any pending Data Lab approvals migrated successfully.
    2. Verify the original systems do not have any data labs configured.