Usage Note 60383: The "...Invalid cursor state..." error occurs when using SAS/ACCESS® Interface to ODBC with the Oracle 12 driver
 |  |  |  |
When using the SQL procedure with SAS/ACCESS Interface to ODBC, you might receive the following error:
ERROR: CLI describe error: [Oracle][ODBC]Invalid cursor state.
You encounter this problem when you use UNIX platforms with the Oracle 12 driver.
When using a LIBNAME statement, you receive an error stating that the table does not exist. The error occurs when you use UTF-8 encoding.
To circumvent the problem, set the environment variable in your sasenv_local file as shown below:
export EASYSOFT_UNICODE=yes
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to ODBC | 64-bit Enabled AIX | 9.4_M4 | 9.4 TS1M4 | ||
| 64-bit Enabled Solaris | 9.4_M4 | 9.4 TS1M4 | ||||
| HP-UX IPF | 9.4_M4 | 9.4 TS1M4 | ||||
| Linux for x64 | 9.4_M4 | 9.4 TS1M4 | ||||
| Solaris for x64 | 9.4_M4 | 9.4 TS1M4 | ||||
When using the UTF-8 encoding with SAS/ACCESS Interface to ODBC and the Oracle 12 driver, you might receive an "...invalid cursor state..." error. To circumvent the problem, set the environment variable EASYSOFT_UNICODE to YES.
| Type: | Usage Note |
| Priority: |
| Date Modified: | 2017-05-30 13:27:40 |
| Date Created: | 2017-05-01 09:54:45 |