db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5528) DRDA problem via DB2 client: SQL0901N SQLSTATE=58004
Date Tue, 07 Feb 2012 16:42:59 GMT

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

Kathey Marsden commented on DERBY-5528:
---------------------------------------

Hello Andres,

I am sorry I closed your issue so abruptly without full explanation. I thought it was a different
one that had been discussed somewhat at length.

Support by IBM for DB2 Runtime Client with Derby was available Windows only  and compatible
a single Derby release 10.1 and then removed with this announcement in 2007. https://www-304.ibm.com/support/docview.wss?uid=swg21303827
as it was just not viable to or good for the community to keep a closed source product in
sync with an open source one and with that announcement there was no support mechanism for
it.

As for DRDA, DRDA protocol is a not as portable as you might think. All implementations including
Derby use stored procedures and DRDA extensions to accomplish things like large object operations,
etc.  These implementations  are not known to all clients only ones that  specifically are
implemented to work with Derby. RIght now I think only Derby Client falls into that category
of a working network client.  Also there has been discussion in the community about deviating
from the DRDA  standard where it makes sense and I think there are already cases where that
has been done.

I totally agree, that communication needs to be clearer so people don't head down this dead
end path. The article you referenced has been removed and Stan Bradbury at IBM is working
to do a more thorough search and removal.  Also  I filed https://issues.apache.org/jira/browse/DERBY-5565
to reject all clients that are not derby client. If someone wants to make an open source ODBC
client someday to connect they can added. 

 
Best 

Kathey
                
> DRDA problem via DB2 client: SQL0901N SQLSTATE=58004
> ----------------------------------------------------
>
>                 Key: DERBY-5528
>                 URL: https://issues.apache.org/jira/browse/DERBY-5528
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Client
>            Reporter: Andres Gomez Casanova
>              Labels: client, db2, drda
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Hi,
> I am trying to connect to Derby via DRDA and then via ODBC. To do this, I use the DB2
runtime client that is DRDA compatible.
> I cataloged the Derby instance and the database. However, I cannot use the database from
ODBC.
> I follow an explanation from IBM, but I cannot get the database because of a DRDA AD
problem (Paser Invalid Value)
> I would like to know if Derby is completely compatible with DRDA.

--
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