Usage Note 49767: When using SAS/ACCESS® Interface to Teradata, you might receive the error "Could not find opermsg.cat"
When using SAS/ACCESS Interface to Teradata, you might receive the following message:
ERROR: Teradata connection: Could Not Find Message Catalog opermsgs.cat Correct error and restart as an APPEND process with option TPT_RESTART=YES. Since no checkpoints were taken, if the previous run used FIRSTOBS=n, use the same value in the restart.
The problem occurs when the NLSPATH variable does not have the proper path for the opermsg.cat file that is provided with the Teradata client.
To resolve the problem, set your environment variable for NLSPATH similar to the example below:
export NLSPATH=/opt/teradata/client/13.10/tbuild/msg/%N:/opt/teradata/client/13.10/odbc_32/msg/%N:$NLSPATH
The %N parameter is very important. If you simply set the NLSPATH to the MSG directory, it will fail and return the error.
Operating System and Release Information
| SAS System | SAS/ACCESS Interface to Teradata | 64-bit Enabled AIX | 9.2 TS2M3 | |
| 64-bit Enabled HP-UX | 9.2 TS2M3 | |
| 64-bit Enabled Solaris | 9.2 TS2M3 | |
| HP-UX IPF | 9.2 TS2M3 | |
| Linux | 9.2 TS2M3 | |
| Linux for x64 | 9.2 TS2M3 | |
| Solaris for x64 | 9.2 TS2M3 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When using SAS/ACCESS Interface to Teradata, you can receive "Could Not Find Message Catalog opermsgs.cat" messages. The problem occurs when the NLSPATH environment variable is not set properly. To resolve the problem, make sure that the NLSPATH includes the TBUILD library with the %N parameter.
| Date Modified: | 2013-08-12 17:04:08 |
| Date Created: | 2013-04-26 14:19:14 |
