db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5551) DB2 .NET Data Provider no longer able to connect.
Date Thu, 22 Dec 2011 09:36:38 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174720#comment-13174720
] 

Kristian Waagan commented on DERBY-5551:
----------------------------------------

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.
                
> DB2 .NET Data Provider no longer able to connect.
> -------------------------------------------------
>
>                 Key: DERBY-5551
>                 URL: https://issues.apache.org/jira/browse/DERBY-5551
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.8.1.2, 10.8.2.2
>         Environment: Network Server running on any platform (Tested on Windows 2003 Server
and Fedora 14 Linux) using IBM JRE (1.6.0 SR9)
> DB2 .NET Data Provider running on Windows 2003 Server
>            Reporter: Ben Hardill
>         Attachments: Derby.NET-Test.zip, Server1.trace, derby-sysinfo
>
>
> While looking for a solution for connecting a .NET C# application to a Derby database
I tried the DB2 .NET Data Provider. I thought this might work since both DB2 and Derby both
use DRDA and that the DB2 JDBC driver will happily connect to Derby as well.
> I had 2 different Derby instances that I used to test this and one worked just fine and
the other would fail to connect with the following error:
> ERROR [58004] [IBM] SQL0901N  The SQL statement failed because of a non-severe system
error. Subsequent SQL statements can be processed.  (Reason "DRDA AR: Parser Invalid Value".)
 SQLSTATE=58004
> Investigation showed that the failing instance was using the latest Derby version (10.8.2.2)
and the working version was using an older build (10.6.1.0). Trying the release versions in
order shows that the regression happens with the release builds 10.8.1.2 and later. 
> The DB2 .NET Data Provider can be downloaded here:
> http://www-01.ibm.com/software/data/db2/ad/dotnet.html
> A quick sample app can be found here:
> http://www.hardill.me.uk/Derby.NET-Test.zip 
> You can run it as follows:
> TestDB2Connection.exe -host 192.168.229.1 -port 1547 -database IPA -user user -password
foo -query "select * from APP.PERSONS"
> It outputs a CSV dump of the result set

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message