Topic
  • 1 reply
  • Latest Post - ‏2012-03-31T16:14:08Z by davbrown2
SystemAdmin
SystemAdmin
1525 Posts

Pinned topic Problem connecting to Derby from DB2 client

‏2011-12-13T13:19:59Z |
Hi,

I read this article

http://www.ibm.com/developerworks/data/library/techarticle/dm-0409kartha/

and I tried to follow the instruction, however I have problems to do the connection successfully. I got this error


SQL0901N 
"drda ar parser invalid value" sqlstate=58004


I am using Data Server client 9.7.4 (DB2 client) and Apache Derby 10.8.2.2.

I would like to know if those instructions are still valid for the recent versions, because the article is a quite old (2004)
Updated on 2012-03-31T16:14:08Z at 2012-03-31T16:14:08Z by davbrown2
  • davbrown2
    davbrown2
    1 Post

    Re: Problem connecting to Derby from DB2 client

    ‏2012-03-31T16:14:08Z  
    We just encountered this problem.

    searching for the error message, I turned up some some forum postings and a Derby problem report from December:

    https://issues.apache.org/jira/browse/DERBY-5551

    • the problem was introduced very recently - it occurs only in 10.8.1.2 & 10.8.2.2
    • response from the Derby project is "The only client currently supported with Derby is the Derby java client. So I think we need to close this issue invalid. "

    and this recommendation ((the original poster was using the IBM DB2 .NET Data Provider)

    "There seems to be solutions for using JDBC with .NET, where you are able to use the JDBC drivers from within .NET. I'm not familiar with .NET, so I don't know if using these are cumbersome or has major drawbacks.
    For other scenarios there are ODBC-JDBC bridges. I've only found commercial offerings that mention support for Apache Derby, but I know nothing about this in general."

    I would be interested in hearing if anyone has come up with any solutions.

    We encountered this problem using ODBC (IBM DB2 ODBC driver), which works fine with earlier versions of Derby. I work for StarQuest - our own JDBC driver (StarSQL for Java) can still connect OK; I haven't tried the IBM JDBC (JCC) driver yet (and of course the Derby JDBC driver should be expected to work). The commercial ODBC-JDBC bridge referred to is from EasySoft.