Troubleshooting Job-Stream Failure - BAR

Teradata Appliance Backup Utility Installation and User Guide

Product
BAR
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-07-13
dita:mapPath
dhb1488824663275.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-3134
lifecycle
previous
Product Category
Teradata Tools and Utilities
Job-stream failure results from an ARC-to-server timeout and suggests that a problem has occurred with the ARC stream trying to connect to the Appliance Backup Utility server. The Appliance Backup Utility GUI displays the stream in the Connecting state for 5 minutes before the job stream fails. This symptom normally occurs after a recent installation or reconfiguration of the Appliance Backup Utility or Teradata ARC.

Try each of the following steps, in the following order, to determine the cause of the job stream failure.

  1. Verify that ARC output (.out) files are being created in the Appliance Backup Utility user home directory, /home/abuservice. If .out files do not exist, Teradata ARC was not launched. This indicates that the Appliance Backup Utility cannot find the ARCMAIN binary, the permission on the Teradata ARC launch script is incorrect, or the Appliance Backup Utility client on the node was unable to establish a connection with the Appliance Backup Utility server.
  2. [Optional] If an ARC .out file exists and has a matching timestamp of the attempted launch, open and examine the ARC log for client errors.
  3. [Optional] If an ARC .out file does not exist, or an .out file of 0 bytes exists, examine the Teradata ARC launch script:
    1. Verify that the proper permissions and owners are assigned to the runarc.bat file: -rwxr-xr-x 1 abuservice root 2274 Jul 17 15:26 runarc.bat
    2. Determine whether runarc.bat locates the ARCMAIN binary:
      rpm -q --queryformat '%{INSTALLPREFIX}\n' teradata_arc
      If the following output results, Teradata ARC might not launch. As a result, jobs in the Appliance Backup Utility GUI could remain in the connection phase, and the ARC .out file could remain a zero-length file:
      (none)
      (none)
    3. Verify that there is a valid link to the ARCMAIN utility:
      ls -l /usr/bin/arcmain
      lrwxrwxrwx 1 root root 37 Feb 26 10:39 /usr/bin/arcmain ->
      /opt/teradata/client/16.10/bin/arcmain
    4. [Optional] If the link does not exist but the rpm display in step a shows a path, create a link to it:
      ln -s /opt/teradata/client/16.10/bin/arcmain /usr/bin/arcmain
  4. [Optional] Verify that the server's home directory has read, write, and execute permissions for the Appliance Backup Utility user account. The next example shows a valid home directory where abuservice is configured as the Appliance Backup Utility user account:
    barlnx1:/home # ls -ld abuservice
    drwxr-xr-x 3 abuservice root 16032 Apr 26 07:20 abuservice