Re: [-3102]: Invalid subtrans structure / update / column of type LONG / JDBC

Hi,

we also had this error after upgrading to MaxDB 7.5.0.34
We opened a ticket at Sap-Support and the result was a bug report for MaxDB.
Have a look at the following document (and try the workaround ;-) ):

http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1142714


bye-----GERD-----


[email protected] schrieb:
> Hello,
> 
> By the way: I guess that the reason for this error is the same like the 
> one that I reported yesterday (Thread: Re: Strange: Error -7065 SAP 
> DBTech SQL: [-7065] SUBTRANS COMMIT/ROLLBACK).
> 
> I did not yet have a look at the implementation for these methods:
> 
>  PreparedStatement prep = ...; prep.setBytes(int parameterIndex, byte 
> x[]); prep.executeUpdate();
> 
> But what I guess is, that writing the byte[] to the database is somehow 
> handled asynchronously but not Thread save.
> 
> If I can provide code/a JDBC trace to reproduce the problem, I'll do, of 
> course. Unfortunately I failed to reproduce the problem by extracting 
> the portion of code that should produce the error (perhaps because it 
> depends on the timing between the call of these statements).
> 
> Best regards,
> Gabriel Matter
> 
> Schroeder, Alexander wrote:
>> Hello,
>>
>> could you run the example with a JDBC trace? (And supply a definition 
>> of the
>> table that is affected?)
>>
>> Regards
>> Alexander Schröder
>> SAP DB, SAP Labs Berlin
>>
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] Sent: Donnerstag, 4. 
>> Mai 2006 16:05
>> To: [email protected]
>> Subject: [-3102]: Invalid subtrans structure / update / column of type 
>> LONG
>> / JDBC
>>
>> Hello,
>>
>> I guess that there is a bug that causes the above exception (error 
>> message "[-3102]: Invalid subtrans structure") when a row containing a 
>> column of type LONG is updated. But it seems that this error is thrown 
>> only under certain conditions.
>>
>> - the exception occurs only if the value of the LONG-column is NOT NULL.
>> - the exception is thrown only when using a certain sequence of 
>> statements.
>>
>> In our example the exception is thrown using the following sequence:
>>
>> SELECT: we read the last row's primary key of that table
>> INSERT: we insert the new row containing some data for the column of 
>> type LONG [prep.setBytes(byte[])]
>> UPDATE: we update the inserted row while all non-key columns are 
>> updated (altough the byte[]-content remains the same)
>>
>> -> If we place another SELECT-statement between the above INSERT and 
>> UPDATE statement that reads the inserted row from the database, the 
>> exception is *not* thrown.
>>
>> -> Altough the exception is thrown, the update is done correctly in 
>> our example
>>
>> We use JDBC driver 7.6.0   Build 012-000-004-339 on MaxDB Kernel 7.5.0 
>> Build 034-121-118-234
>>
>> I found that there was a similar problem posted on 2003-03-03 and 
>> possibly the same problem was the cause of this report: 
>> http://lists.mysql.org/maxdb/19277 (28.11.2003)
>>
>> Perhaps I'll be able to post a program/tabledefinition that can 
>> reproduce the problem.
>>
>> Best regards,
>> Gabriel Matter
>>   
> 
> 


-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[email protected]