Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Wed, 18 Sep 2003 @ 00:51:29 GMT

  <Prev Next>   <<First <Prev Next> Last>>  

Subj:   Re: Teradata CLIv2 Errors
From:   Andy Baker


Just guessing but you are probably getting TEradata CLI errors but the CLI cannot find the error library to resolve them into messages.

There used to be a COPLIB and COPERR environment variable that point to directories where the clipsb (the default options such as the default tdpname) and error messages are on the CLient

Maybe someone moved the directories

Have just looked at the JDBC manual - Appendix A

The COPERR parameter describes the path of the CLIv2 error message text file, errmsg.txt on UNIX systems.

If the gateway is running on a UNIX system and you see the error message 'No such error found,' make sure that the COPERR parameter has the correct path to the error message text file, errmsg.txt:

Step Action

1 Check the /usr/lib subdirectory to determine the location of the errmsg.txt file.

2 Where ed (error directory) is the path of the directory where the errmsg.txt file is located, enter the following commands to define the COPERR parameter:

- For Bourne shell systems, add the following to the .profile file:

COPERR=/ed;export COPERR

- For C shell systems, add the following to the .login file:

setenv COPERR /ed

3 After making the changes, run the .profile or .login file.


Andy Baker

  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 28 Jun 2020