Re: [MonetDB-users] Extended Fetch ODBC Error
Hi Sjoerd, Would it be possible to test your thesis ? The OBI guys reckon that for odbc 2 connections, they use the function SQLExtendedFetch. This has bee replaced by SQLFetchScroll in odbc 3.5. Not sure if that helps, I know little or nothing about odbc, other than many BI tools only use this interface and not jdbc. Regards, Jeremy It is unclear from this message what exactly fails. My guess (since I saw something like that recently) is that Oracle's OBI EE tries to set the statement option (or attribute) SQL_ATTR_CONCURRENCY to a value that is not supported. We only support setting the value to SQL_CONCUR_READ_ONLY. Attempting to set the attribute to any other value will return the above error (not implemented). Perhaps what we should do instead here is accept the value and return a message (in the ODBC way) that instead of the value that the application asked for we set it to SQL_CONCUR_READ_ONLY. Other possible statement attributes that could return the feature not implemented error are SQL_ATTR_ASYNC_ENABLE, SQL_ATTR_CURSOR_SENSITIVITY, SQL_ATTR_ENABLE_AUTO_IPD, SQL_ATTR_FETCH_BOOKMARK_PTR, SQL_ATTR_KEYSET_SIZE, SQL_ATTR_MAX_LENGTH, SQL_ATTR_MAX_ROWS, SQL_ATTR_QUERY_TIMEOUT, SQL_ATTR_ROW_NUMBER, SQL_ATTR_SIMULATE_CURSOR, and SQL_ATTR_USE_BOOKMARKS. On 9 Nov 2011, at 12:26, Jeremy O'Sullivan wrote:
Hello,
When trying to connect to MonetDB using Oracle's OBI EE, I get the error below. Has anyone seen this before ? Regards, Jeremy
[MonetDB][ODBC Driver 11.5.7]Optional feature not implemented.
[nQSError: 16006] Setting the statement option for extended fetch failed.
On 2011-11-09 18:35, Jeremy O'Sullivan wrote:
Hi Sjoerd, Would it be possible to test your thesis ? The OBI guys reckon that for odbc 2 connections, they use the function SQLExtendedFetch. This has bee replaced by SQLFetchScroll in odbc 3.5. Not sure if that helps, I know little or nothing about odbc, other than many BI tools only use this interface and not jdbc. Regards, Jeremy
You could ask the ODBC driver to provide a log. You can do this by starting your application with an extra environment variable: Set ODBCDEBUG to an absolute path name of a file that you can write (i.e. a location where you can create and write a file). Then start the application. When the application is finished, the file should contain the log. Probably the easiest way is to start a cmd.exe (Start menu -> Run, then type cmd.exe) and in the window type set ODBCDEBUG=C:\...\odbc.log c:\...\application.exe
It is unclear from this message what exactly fails. My guess (since I saw something like that recently) is that Oracle's OBI EE tries to set the statement option (or attribute) SQL_ATTR_CONCURRENCY to a value that is not supported. We only support setting the value to SQL_CONCUR_READ_ONLY. Attempting to set the attribute to any other value will return the above error (not implemented).
Perhaps what we should do instead here is accept the value and return a message (in the ODBC way) that instead of the value that the application asked for we set it to SQL_CONCUR_READ_ONLY.
Other possible statement attributes that could return the feature not implemented error are SQL_ATTR_ASYNC_ENABLE, SQL_ATTR_CURSOR_SENSITIVITY, SQL_ATTR_ENABLE_AUTO_IPD, SQL_ATTR_FETCH_BOOKMARK_PTR, SQL_ATTR_KEYSET_SIZE, SQL_ATTR_MAX_LENGTH, SQL_ATTR_MAX_ROWS, SQL_ATTR_QUERY_TIMEOUT, SQL_ATTR_ROW_NUMBER, SQL_ATTR_SIMULATE_CURSOR, and SQL_ATTR_USE_BOOKMARKS.
On 9 Nov 2011, at 12:26, Jeremy O'Sullivan wrote:
Hello,
When trying to connect to MonetDB using Oracle's OBI EE, I get the error below. Has anyone seen this before ? Regards, Jeremy
[MonetDB][ODBC Driver 11.5.7]Optional feature not implemented.
[nQSError: 16006] Setting the statement option for extended fetch failed.
------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- Sjoerd Mullender
participants (2)
-
Jeremy O'Sullivan -
Sjoerd Mullender