During DSA component installation, user accounts, initialization scripts, and environmental variables are created. You can verify proper installation by checking for these items.
- Verify that the ClientHandler web service is listening on all media servers by typing # netstat -an | grep 15402 | grep LISTEN.
Verify that the DSA components exist in the following file paths:
Package/Script File Path DSC Package /opt/teradata/client/version/dsa/dsc DSC Service Initialization Script /etc/init.d/dsc BAR Client Handler Package base_dir/teradata/client/version/dsa/clienthandler BAR Client Handler Service Initialization /etc/init.d/clienthandler BAR Command-Line Package base_dir/teradata/client/version/dsa/commandline
Verify that the DSCUSER was created with the proper uid.
# id -u dscuserThe response should be positive and return the uid configured during install time.
Restart the session and verify that the following environmental variables were created:
Environment Variable Setting DSA_CONFIG_DIR /etc/opt/teradata/dsa DSA_LOG_DIR /var/opt/teradata/dsa/logs DSA_LOG_LANDING_ZONE_DIR /var/opt/teradata/dsa/landing_zone DSA_DSC_ROOT base_dir/teradata/client/version/dsa/dsc CLIENTHANDLER_ROOT base_dir/teradata/client/version/dsa/clienthandler BARCMDLINE_ROOT base_dir/teradata/client/version/dsa/commandlinebase_dir and version are resolved at install time. The PATH environmental variable is configured with the paths to dsc.sh and dsc for the BAR command line.