Problem Note 51592: When you use SAS/ACCESS® Interface to ODBC on a UNIX platform, character data is truncated to 0
Using SAS/ACCESS Interface to ODBC to bring data into SAS might result in character data being truncated to 0 values. A note similar to the following might appear in the log:
NOTE: The data value for column Name (Name) was truncated
or was out of range ## times when retrieving that data from the DBMS.
This behavior occurs because the "_u" modules are linked in the !SASROOT/sasexe directory and the following conditions are also true:
- The Driver Manager is unixODBC.
- SAS is running on a UNIX platform.
Are the _u modules Linked?
To determine whether the _u modules are linked on a UNIX platform, issue this command from the
!SASROOT/SASFoundation/9.x/sasexe directory:
ls -lrt sasodb sasioodb
If the command results in the following, then the _u modules are linked:
sasodb->sasodb_u
sasioodb->sasioodb_u
Correcting the Issue
If the above conditions are met, your next step toward correcting the issue requires investigation into why the _u modules are in place.
The _u modules are not linked by default. It is a manual process that someone has to perform. They are 64-bit modules designed to work with 64-bit drivers that still have 32-bit internal calls. Without the _u modules linked for a driver that requires them, a LIBNAME connection generally throws a segmentation fault when submitted. The most common driver that needs these _u modules is DB2 (libdb2.so).
If the _u modules are linked for use with the DB2 driver, you should be able to change the driver from "libdb2.so" to "libdb2o.so" and then replace the _u modules with the original modules.
If the driver requiring the _u modules is not the DB2 driver specified above, you will need to ask the vendor whether they have an updated driver.
If SAS has an ACCESS product specifically for one or the other databases, you might consider using it instead. And finally, if you determine that the only solution is to continue to use both drivers (one needing _u modules and the other needing the original modules), consider creating a new context server in SAS® Management Console to include the correct modules.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to ODBC | AIX | | |
HP-UX IPF | | |
Linux | | |
Linux for x64 | | |
Solaris | | |
Solaris for x64 | | |
*
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.
Type: | Problem Note |
Priority: | medium |
Topic: | Data Management ==> Data Sources ==> External Databases ==> ODBC (Open Database Connectivity)
|
Date Modified: | 2013-12-12 15:08:56 |
Date Created: | 2013-11-12 15:16:20 |