[
https://issues.apache.org/jira/browse/OOZIE-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695708#comment-13695708
]
Rohini Palaniswamy commented on OOZIE-1436:
-------------------------------------------
+1
> Revert SLA_XML and few other varchar columns back to clob
> ---------------------------------------------------------
>
> Key: OOZIE-1436
> URL: https://issues.apache.org/jira/browse/OOZIE-1436
> Project: Oozie
> Issue Type: Bug
> Reporter: Virag Kothari
> Assignee: Virag Kothari
> Fix For: trunk
>
> Attachments: OOZIE-1436.patch
>
>
> OOZIE-1398 converts few columns from clobs to varchar(4000). But there seems
> to be problem where (@lenght=4000) annotation is not working and trying to
> insert more than 1000 chars throws ORA-24816 with Oracle. Though it seems a
> oracle problem from the error code, it is actually not as trying to do a
> direct insert with more than 1000 chars in Oracle works. Also openjpa does
> map to varchar2(4000) when creating schema. But somehow openjpa only accepts
> upto 1000 chars and nothing more when trying to insert.
> Have posted on openjpa user list with no reply yet. Thread at
> http://openjpa.208410.n2.nabble.com/ORA-24816-column-ordering-during-inserts-td7584233.html
> This jira will revert sla_xml and data varchar columns back to clob
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
