[ http://issues.apache.org/jira/browse/DERBY-745?page=comments#action_12365147 ]
Kathey Marsden commented on DERBY-745: -------------------------------------- Thanks Bryan for looking at this issue. If I try to create the table with DB2, I get an error SQLSTATE 54010 Table record length is too long. So, there is definitely more investigation needed from the jcc side if this is to work with Derby. The SYSSTAT package that refers to the static functions that are supposed to be built in but I think does not correspond to the schema. The metadata calls for instance would be sent with package SYSSTAT but the procedure name would be SYSIBM.GETTABLES() for instance. If there is no procedure name in the EXCSQLSTT call, I am not sure what JCC is trying to call in this case, but will pass on to those who might be able to find out. A little background on some of the package names is available at: http://publib.boulder.ibm.com/infocenter/db2luw/v8//topic/com.ibm.db2.udb.doc/ad/r0007866.htm?resultof=%22%53%59%53%53%54%41%54%22%20%22%73%79%73%73%74%61%74%22%20%22%70%61%63%6b%61%67%65%22%20%22%70%61%63%6b%61%67%22%20%22%69%73%6f%6c%61%74%69%6f%6e%22%20%22%69%73%6f%6c%22%20%22%6c%65%76%65%6c%22%20 > DRDA Protocol Exception using DB2JCC driver and CLOBs from IJ > ------------------------------------------------------------- > > Key: DERBY-745 > URL: http://issues.apache.org/jira/browse/DERBY-745 > Project: Derby > Type: Bug > Components: Network Server > Versions: 10.1.1.0 > Reporter: Bryan Pendleton > Assignee: Bryan Pendleton > Priority: Minor > > Trying to manipulate a cursor via IJ using the DB2JCC driver talking to the > Network Server encounters a DRDA Protocol Exception: > ERROR 58009: Execution failed due to a distribution protocol error that > caused deallocation of the conversation. A DRDA Data Stream Syntax Error was > detected. Reason: 0x2113 > Here is how to reproduce the problem: > 1) Start the Network Server, including derbyTesting.jar in your classpath > 2) Create a database. In my script below I called the database 'testBig', but > you can use any name, just tweak the connect statement below > 3) Start IJ, being sure that > a) db2jcc.jar and db2jcc_license_c.jar are in your path > b) you are authenticated (-Dij.user=APP -Dij.password=APP in the simple > case) > 4) Run the following small script. The error occurs on the 'first c1' line. > driver 'com.ibm.db2.jcc.DB2Driver'; > connect 'jdbc:derby:net://localhost:1527/testBig'; > create procedure INSERTDATA1(IN a int) language java parameter style java > external name > 'org.apache.derbyTesting.functionTests.util.ProcedureTest.bigTestData'; > prepare p1 as 'call INSERTDATA1(?)'; > drop table big; > create table big(c1 clob(40000), c2 clob(40000), c3 clob(40000)); > execute p1 using 'values 8'; > get scroll insensitive cursor c1 as 'select * from big'; > first c1; > quit; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
