Looks like the full/lite DB2 8.2 runtime client connects to derby 10.5.3.0 fine but has trouble recognizing table names with an underscore. So I had to configure CLI and add a keyword 'UNDERSCORE' with a '0' value to allow ODBC see these tables from derby.
This topic has been locked.
3 replies Latest Post - 2010-06-17T16:58:17Z by Stan
Ed Yu 270002YVNT
Pinned topic DB2 8.2 Runtime Client ODBC connection to Derby 10.5.3.0
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2010-06-17T16:58:17Z at 2010-06-17T16:58:17Z by Stan
firstname.lastname@example.org 120000F75T2 Posts
Stan 120000HAGM267 PostsACCEPTED ANSWER
Re: DB2 8.2 Runtime Client ODBC connection to Derby 10.5.3.02010-06-17T16:58:17Z in response to email@example.comIntegration was provided between IBM Cloudscape and the DB2 Runtime Clinet to support ODBC until IBM Cloudscape was discontinued after the 10.1 release (http://www-01.ibm.com/common/ssi/rep_ca/0/897/ENUS907-040/ENUS907040.PDF).
Because IBM Cloudscape was an unaltered release of Apache Derby the DB2 CLI worked smoothly with Derby 10.0 and 10.1. After that the integration has not been maintained and I would expect increasing problems with using the DB2 CLI with each new release of Derby.