Bug 1037571 - BPEL riftsaw-ode - IBM DB2 SQL schema fails to load. Column (BPEL_FAULT.MESSAGE) larger than allowable value.
Summary: BPEL riftsaw-ode - IBM DB2 SQL schema fails to load. Column (BPEL_FAULT.MESSA...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: BPEL Integration
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER7
: 6.0.0
Assignee: Steve Johnson
QA Contact: lvaskova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-03 11:52 UTC by Steve Johnson
Modified: 2014-05-12 09:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RIFTSAW-550 0 Major Resolved IBM DB2 Column Size Patch 2014-06-04 11:20:02 UTC

Description Steve Johnson 2013-12-03 11:52:35 UTC 
Description of problem:

The IBM DB2 generated SQL for riftsaw-ode fails due to column size being larger than column max allowable value.

See BPEL_FAULT.MESSAGE mapped from class dao-jpa/src/main/java/org/apache/ode/dao/jpa/bpel/FaultDAOImpl.java

The value is set to 102400 and the largest acceptable column size for varchar type is 32 672 bytes long.

The solution is to apply @Lob annotation and map the java attribute to clob type.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Steve Johnson 2013-12-03 16:31:03 UTC 
IBM DB2 now maps this column to "clob" type that supports 102400 bytes.

Patch applied at productisation build time and generated SQL ran into db2 database instance.  Needs to be pushed back to community team at the next appropriate point.
Comment 2 lvaskova 2013-12-18 12:36:03 UTC 
Verified on ER7
Comment 3 JBoss JIRA Server 2014-05-12 09:06:10 UTC 
Gary Brown <gary> updated the status of jira RIFTSAW-550 to Resolved
Note You need to log in before you can comment on or make changes to this bug.