Usage Note 60317: The "...Cursor xxxxx not open..." error occurs when using SAS/ACCESS® Interface to ODBC
 |  |  |  |
When reading tables using SAS/ACCESS Interface to ODBC, you might receive the following error:
ERROR: CLI cursor extended fetch error: [IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL0501
- Cursor SQL_CUR0ABB58E0 not open
- Cursor SQL_CUR0ABB58E0 not open
This error occurs when you use SAS/ACCESS Interface to ODBC with an IBM DB2 driver.
To circumvent the error, specify CURSOR_TYPE=STATIC in your LIBNAME statement.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to ODBC | Microsoft® Windows® for 64-Bit Itanium-based Systems | ||
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | ||||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | ||||
| Microsoft Windows XP 64-bit Edition | ||||
| Microsoft® Windows® for x64 | ||||
| OS/2 | ||||
| Microsoft Windows 8 Enterprise 32-bit | ||||
| Microsoft Windows 8 Enterprise x64 | ||||
| Microsoft Windows 8 Pro 32-bit | ||||
| Microsoft Windows 8 Pro x64 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | ||||
| Microsoft Windows 8.1 Enterprise x64 | ||||
| Microsoft Windows 8.1 Pro 32-bit | ||||
| Microsoft Windows 8.1 Pro x64 | ||||
| Microsoft Windows 10 | ||||
| Microsoft Windows 95/98 | ||||
| Microsoft Windows 2000 Advanced Server | ||||
| Microsoft Windows 2000 Datacenter Server | ||||
| Microsoft Windows 2000 Server | ||||
| Microsoft Windows 2000 Professional | ||||
| Microsoft Windows NT Workstation | ||||
| Microsoft Windows Server 2003 Datacenter Edition | ||||
| Microsoft Windows Server 2003 Enterprise Edition | ||||
| Microsoft Windows Server 2003 Standard Edition | ||||
| Microsoft Windows Server 2003 for x64 | ||||
| Microsoft Windows Server 2008 | ||||
| Microsoft Windows Server 2008 R2 | ||||
| Microsoft Windows Server 2008 for x64 | ||||
| Microsoft Windows Server 2012 Datacenter | ||||
| Microsoft Windows Server 2012 R2 Datacenter | ||||
| Microsoft Windows Server 2012 R2 Std | ||||
| Microsoft Windows Server 2012 Std | ||||
| Microsoft Windows XP Professional | ||||
| Windows 7 Enterprise 32 bit | ||||
| Windows 7 Enterprise x64 | ||||
| Windows 7 Home Premium 32 bit | ||||
| Windows 7 Home Premium x64 | ||||
| Windows 7 Professional 32 bit | ||||
| Windows 7 Professional x64 | ||||
| Windows 7 Ultimate 32 bit | ||||
| Windows 7 Ultimate x64 | ||||
| Windows Millennium Edition (Me) | ||||
| Windows Vista | ||||
| Windows Vista for x64 | ||||
When using SAS/ACCESS Interface to ODBC with an IBM DB2 driver, you might encounter "ERROR: CLI cursor extended fetch error: [IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL0501- Cursor SQL_CUR0ABB58E0 not open." To circumvent the error, specify CURSOR_TYPE=STATIC in your LIBNAME statement.
| Type: | Usage Note |
| Priority: |
| Date Modified: | 2017-04-24 16:32:59 |
| Date Created: | 2017-04-19 12:18:57 |