[infinispan-issues] [JBoss JIRA] (ISPN-2082) JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes

[Thomas Fromm (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706279#comment-12706279 ] 

Thomas Fromm commented on ISPN-2082:
------------------------------------

Thanks, can confirm it. Its working on normal Oracle installation and fails on RAC :-o
I can't agree with Mircea introducing a new database type. The easiest solution would be reordering the fields in general. 
If this is considered too dangerous, at least insert/updates for oracle should be changed, because both orders works on normal oracle installations. 
                
> JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes
> --------------------------------------------------------------------------
>
>                 Key: ISPN-2082
>                 URL: https://issues.jboss.org/browse/ISPN-2082
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Loaders and Stores
>    Affects Versions: 5.1.5.FINAL
>         Environment: OS X 10.7.4, JDK 1.7.0u4
>            Reporter: Ryan Scharer
>            Assignee: Tristan Tarrant
>             Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL
>
>
> I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a BLOB value column.  If I try to store a BLOB value of less than 4000 bytes, everything works fine.  If the value is greater, the cache store fails with ORA-24816.  This occurs because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle driver requires.  My current, sad workaround is to clone the JdbcStringBasedCacheStore implementation and write my own insert/update SQL in storeLockSafe().  This works fine, but obviously isn't ideal from an upgrade point of view.  Simply overriding storeLockSafe() isn't an option due to all the private fields.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira