[
https://issues.apache.org/jira/browse/DERBY-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5528:
---------------------------------
Urgency: Normal
Issue Type: Improvement (was: Bug)
I am re-classifying this issue as an enhancement request rather than a bug.
Derby uses a network protocol which is based on DRDA. No effort has been put
into measuring or describing Derby's divergence from standard DRDA. By now I am
fairly sure that Derby diverges from standard DRDA in many ways.
> 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
