[jira] Assigned: (DERBY-745) DRDA Protocol Exception using DB2JCC driver and CLOBs from IJ

["Bryan Pendleton (JIRA)" <de...@db.apache.org>]

     [ http://issues.apache.org/jira/browse/DERBY-745?page=all ]

Bryan Pendleton reassigned DERBY-745:
-------------------------------------

    Assign To: Bryan Pendleton

> 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