db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Army <a...@golux.com>
Subject Re: [jira] Created: (DERBY-93) Cannot connect to Derby using DB2 Universal Driver
Date Tue, 07 Dec 2004 21:42:54 GMT
Raj Subramani (JIRA) wrote:
> Cannot connect to Derby using DB2 Universal Driver
> --------------------------------------------------
[ snip ]
> As per the Server & Admi guide, the Derby network server should be accesible using
the DB2 Universal Driver.
> namely, db2jcc.jar db2jcc_license_c.jar
> 
> I have a (licensed) copy of the above driver which which I am able to connect to Cloudscape-DB2
v5.1.2.
> 
> Howver using the same driver jars I am unable to connect to Derby
[ snip ]

Hi Raj,

Can you run the Derby "sysinfo" utility and see what version of the DB2 Universal Driver you
have?  If your path is 
setup correctly, you should see something like this in the output:

 > java org.apache.derby.tools.sysinfo

[ snip ]
--------- Derby Information --------
[C:\p4clients\main_army\drda\jcc\2.4\db2jcc.jar] 2.4 - (17)
[C:\p4clients\main_army\drda\jcc\2.4\db2jcc_license_c.jar] 2.4 - (17)
------------------------------------------------------
[ snip ]

If the version of the db2jcc files that you're using is earlier than "2.4", then that's the
problem.  JCC versions prior 
to 2.4 only recognize the name "cloudscape", not "derby"--which is why it works when you connect
to a Cloudscape v5.1.2 
database, but not when you try to connect to a Derby database.

 > I then went and downloaded Clodscape 10 and used db2jcc.jar db2jcc_license_c.jar
 > from this distribution.

My guess is that the JCC jars that came with your download for Cloudscape 10 were for "Cloudscape",
not "Derby".  On the 
Apache website, there is a link to a paper on the Universal Driver here:

http://incubator.apache.org/derby/papers/misc.html

Near the bottom, there's a link for "IBM DB2 JDBC Universal Driver", and if you follow that
link, you can find out where 
to download a later version of the Universal Driver--and one that will work with Derby.

Which makes one wonder -- DOCUMENTATION ISSUE?  Should we document the fact that JCC 2.4 is
the minimum required to user 
the Universal Driver for a Derby database?  Or is that documented somewhere already?

Hope that helps,
Army

Mime
View raw message