You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (Commented) (JIRA)" <ji...@apache.org> on 2011/12/09 19:36:40 UTC
[jira] [Commented] (DERBY-5528) DRDA problem via DB2 client:
SQL0901N SQLSTATE=58004
[ https://issues.apache.org/jira/browse/DERBY-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166416#comment-13166416 ]
Kathey Marsden commented on DERBY-5528:
---------------------------------------
I am wondering, what user documentation you are using. A very long time ago, for a very short time there was an effort to get the DB2 ODBC client working with Derby but that has not been supported for years. It would be good to pull any misleading documentation that is out there.
As an aside, even in areas where we are DRDA compliant there are things very particular to Derby that are implemented as stored procedures, for example the stored procedure to retrieve message text or the stored procedures to retrieve partial LOB data, so very specific efforts would need to be made to get any client other than Derby client working with Derby.
> 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