An error might occur when you assign a LIBNAME statement, such as the following, that uses the Netezza engine from SAS Enterprise Guide 4.1:
libname netlib neteeza connection-options;
This statement returns the following error:
An error occurred executing the workspace job "Code".
The server is disconnected.
However, a LIBNAME statement, such as the following, that uses the ODBC engine to access the same Netezza server is successful:
libname odbclib odbc connection-options
After you successfully assign a LIBNAME statement that uses the ODBC engine, you can then re-submit the LIBNAME statement with the Netezza engine, and it will work correctly.
This problem occurs because Netezza 4.0 driver names are the same for both the 32-bit and 64-bit versions. Hence, there might be some confusion when you set the shared library environment variable (for example, LIBPATH=, LD_LIBRARY_PATH=, or SHLIB_PATH=).
When the ODBC engine is used, the driver name is loaded directly from odbc.ini/obdcinst.ini. The system does not have to look at the LIBPATH environment variable. However, when you submit the Netezza engine, the correct driver is already in memory from the previous ODBC connection.
To resolve this problem, set the shared library path to point to the 64-bit Netezza libraries (/nzhome/current/lib64) instead of the 32-bit Netezza libraries (/nzhome/current/lib), as shown in the following examples:
- unix_prompt> export libpath=/nzhome/current/lib64
- unix_prompt> export shlib_path=/nzhome/current/lib64
- unix_prompt> export ld_library_path=/nzhome/current/lib64
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Netezza | 64-bit Enabled AIX | 9.1 TS1M3 SP4 | |
64-bit Enabled HP-UX | 9.1 TS1M3 SP4 | |
64-bit Enabled Solaris | 9.1 TS1M3 SP4 | |
HP-UX IPF | 9.1 TS1M3 SP4 | |
Linux | 9.1 TS1M3 SP4 | |
*
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.