SUPPORT / SAMPLES & SAS NOTES
 

Support

Usage Note 44774: System Requirements for SAS/ACCESS® 9.3 Interface to Greenplum in Windows environments

DetailsAboutRate It

SAS/ACCESS Interface to Greenplum provides access to the EMC Greenplum database.

This product delivers the necessary Open Database Connectivity (ODBC) drivers to connect to Greenplum with the "greenplm" engine. The supplied DataDirect Greenplum ODBC drivers cannot be accessed using the "odbc" engine.

To verify that this product is licensed, invoke SAS and submit the following in the SAS Editor:


   proc setinit noalias; run;

Look in the SASLOG for SAS/ACCESS Interface to Greenplum. If you do not see this product listed, then you do not have the product licensed.

If you see this product listed, verify that you have it installed. Using Windows Explorer, look in the !SASROOT\access\sasexe folder for SASGPL.DLL and SASIOGPL.DLL. If you do not see these files listed, then you do not have this product installed.

Here are the system requirements for using the Windows or Windows for x64 version of SAS/ACCESS Interface to Greenplum:

  • Base SAS® software
  • SAS/ACCESS Interface to Greenplum software

Examples That Illustrate Use of the Greenplum Engine

  • LIBNAME with a DSN
    libname grn1 greenplm dsn=greenplum user=gpuser password=gppass schema=public;
    
  • LIBNAME without a DSN
    libname grn2 greenplm server="gpserver.us.company.com" port=5432 database=gpdb 
    user=gpuser password=gppass schema=public; 
  • Explicit pass-through with a DSN
    proc sql;
    connect to greenplm(dsn=greenplum user=gpuser password=gppass);
    ...
    disconnect from greenplm;
    quit;
    
  • Explicit pass-through without a DSN
    proc sql;
    connect to greenplm(server="gpserver.us.company.com" port=5432 database=gpdb user=gpuser password=gppass);
    ...
    disconnect from greenplm;
    quit;
    

Troubleshooting and Common Errors

Error:
libname myconn greenplum user=dbitest password=XXXXXXX dsn=greenplum schema=public;

WARNING: The name greenplum has been truncated to 8 characters.
ERROR: The GREENPLU engine cannot be found.
ERROR: Error in the LIBNAME statement.

Cause: Misspelling of the engine name. Valid names are "greenplm" or "sasiogpl".

Error:


libname myconn greenplm user=dbitest password=XXXXXXX dsn=greenplum schema=public;

CLI error trying to establish connection: [Microsoft][ODBC Driver Manager] Data source name not
found and no default driver specified
ERROR: Error in the LIBNAME statement.

Cause: A DSN entry has not been defined in the ODBC Data Source Administrator on Windows. Check that there is a DSN entry defined in the Windows ODBC Data Source Administrator and that a test connection can be established.

Note: If SAS is running on Windows x64, the Windows ODBC Data Source Administrator is found in two places.

If SAS is 32-bit, the correct Windows ODBC Data Source Administrator is found here:


C:\Windows\SysWOW64\odbcad32.exe

If SAS is 64-bit, the correct Windows ODBC Data Source Administrator is found here:


C:\Windows\System32\odbcad32.exe

Error:


libname myconn greenplm server="192.168.123.45" port=5432 database=test user=gpuser password=XXXXXXX schema=public;

CLI error trying to establish connection: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
ERROR: Error in the LIBNAME statement.

Cause: The "SAS ACCESS to Greenplum" driver has not been installed. Be sure to follow the directions in the readme.txt file, including making the appropriate manual entries in the Windows registry.

Note: The zip files containing the drivers and readme.txt can be found here:

For 32-bit SAS: !SASROOT\access\sasmisc\w32gplm60.zip
For 64-bit SAS: !SASROOT\access\sasmisc\wx6gplm60.zip

Error:

libname myconn greenplm dsn=greenplum user=dbi password=XXXXXXXX schema=public;

ERROR: CLI error trying to establish connection: [SAS ACCESS to Greenplum]
[ODBC Greenplum Wire Protocol driver][Greenplum]FATAL: role "dbi" does not 
exist(File miscinit.c;Line436;Routine InitializeSessionUserId;) : [SAS 
ACCESS to Greenplum][ODBC Greenplum Wire Protocol driver]Socket closed.
ERROR: Error in the LIBNAME statement.

Cause: The concept of a "role" in Greenplum encapsulates users and groups in the database. The most likely cause of this error is that the user has not been defined in Greenplum.

Error:

The dialog box below appears. SAS code is trying to use the connection to Greenplum:

image label

Cause: Using the "odbc" engine instead of the "greenplm" engine causes this error to occur after the connection to Greenplum has been established and SAS code attempts to use it.

Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS/ACCESS Interface to GreenplumMicrosoft® Windows® for x649.39.3 TS1M0
Microsoft Windows Server 2003 Datacenter Edition9.39.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition9.39.3 TS1M0
Microsoft Windows Server 2003 Standard Edition9.39.3 TS1M0
Microsoft Windows Server 2003 for x649.39.3 TS1M0
Microsoft Windows Server 20089.39.3 TS1M0
Microsoft Windows Server 2008 for x649.39.3 TS1M0
Microsoft Windows XP Professional9.39.3 TS1M0
Windows 7 Enterprise 32 bit9.39.3 TS1M0
Windows 7 Enterprise x649.39.3 TS1M0
Windows 7 Home Premium 32 bit9.39.3 TS1M0
Windows 7 Home Premium x649.39.3 TS1M0
Windows 7 Professional 32 bit9.39.3 TS1M0
Windows 7 Professional x649.39.3 TS1M0
Windows 7 Ultimate 32 bit9.39.3 TS1M0
Windows 7 Ultimate x649.39.3 TS1M0
Windows Vista9.39.3 TS1M0
Windows Vista for x649.39.3 TS1M0
* 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.