Community
Participate
Working Groups
Build Identifier: Eclipselink Version 1.0.0.0_1.0 We have recently restructured our tables to range partitioning on created date (created_dt added to PK), and XML docs are no longer being stored into a CLOB column. Platform: Redhat Linux 2.6.18 Java 1.6_0_2 Oracle database 11.2.0.2 Eclipselink 1.0.0.0_1 jdbc lib -- ojdbc6.jar The JPA logs show this sequence: Execute query InsertObjectQuery(TestBean@c26efe Test Id, [79], Create Date[xxxxxxx], Document[<?xml version=........], JPA Lock[null]) INSERT INTO TEST_TABLE(TEST_ID,CREATED_DT,DOCUMENT,JPA_LOCK)VALUES(?,?,?,?) bind=>[79,2011-03-24 20:29:51, ,1] SELECT DOCUMENT FROM TEST_TABLE WHERE ((TEST_ID = ?) AND (CREATED_DT = ?)) FOR UPDATE bind=> [79, 2011-03-24 20:29:51] This statement occurs next on successful insert of the data in a non-partitioned table, but is not present on partitioned table insert: Writing CLOB value(size = 241 bytes) through the locator to the table field: DOCUMENT We are using these annotations on the Entity @Entity ...... @Lob @Basic(fetch=FetchType.LAZY) @Column(name="DOCUMENT") protected String document_; Reproducible: Always Steps to Reproduce: 1. Insert an Entity into a table which contains a CLOB column 2. 3.
I received a comment from a post to Oracle OTN and following the suggestions, removed the @Lob annotation and problem is solved.
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink