The script that launches Teradata ARC is called runarcnb.bat and is located in /home/baruser. The baruser account must be the owner of this file or Teradata ARC will not launch.
-
Verify that the runarcnb.bat file has the proper permissions and owners assigned to it:
-rwxr-xr-x 1 baruser root 2274 Jul 17 15:26 runarcnb.bat
-
Determine if runarcnb.bat can properly locate the ARCMAIN binary.
The runarcnb.bat script that launches ARC (in /home/baruser) uses a variable called $INSTALLPATH. The variable is defined by executing an rpm -q command to determine where the ARC package is installed:
rpm -q --queryformat '%{INSTALLPREFIX}\n' arcIf the result of this command produces two outputs:
(none)
(none)
ARC might not launch. As a result, jobs in the Teradata TARA GUI could remain in the Connecting phase, and the ARC .out file could remain a zero-length file.
Workaround: Edit the runarcnb.bat script located in the home directory of baruser and replace the INSTALLPATH variable with a hard-coded path to ARCMAIN: /opt/teradata/arc/bin/.
Information on nbubar and taraserver Postscripts Teradata TARA Component Postscript Name and Location Description nbubar /opt/teradata/tara/nbubar/bin/nbubar_postinstall.sh on each media server This postscript creates the correct association between the TARA server and the media server. The postscript also creates, or recreates, runarcnb.bat and nbuquery.bat. IMPORTANT: Before running this script, ensure that you have backed up runarcnb.bat if there have been any edits or changes. Otherwise, the script will be replaced.
taraserver /opt/teradata/tara/server/bin/taraserver_postinstall.sh on the TARA server This postscript defines the name of the TARA server.