Verifying Installation - Data Stream Architecture - Data Stream Utility

Data Stream Utility Installation, Configuration, and Upgrade Guide for Customers

Product
Data Stream Architecture
Data Stream Utility
Release Number
16.00
Published
November 2016
Language
English (United States)
Last Update
2018-04-17
dita:mapPath
lzp1474305417988.ditamap
dita:ditavalPath
3151_DSE_ICUCustomer_1600.ditaval.ditaval
dita:id
B035-3153
Product Category
Software
Teradata Tools and Utilities
During DSA component installation, user accounts, initialization scripts, and environmental variables are created. You can verify proper installation by checking for these items.
  1. Verify that the ClientHandler web service is listening on all media servers by typing # netstat -an | grep 15402 | grep LISTEN.
  2. 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
  3. Verify that the DSCUSER was created with the proper uid.
    # id -u dscuser
    The response should be positive and return the uid configured during install time.
  4. 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/commandline
    base_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.
  5. Validate that the tdbackex scheduler script was installed correctly and linked to the NetBackup file system.

    tdbackex is installed as part of the BARCmdline package. The output from the run_job command executed by the tdbackex script is contained in a log file, /tmp/dsa_tdbackex.log.

    1. If NetBackup was configured on the TMSB server after the command line was installed, create a symbolic link as follows:
      ln -s $BARCMDLINE_ROOT/config/tdbackex /usr/openv/netbackup/bin/tdbackex