Title:
Bug 84553:(Watson Migration Closure)ORM does not properly create blob/clob fields in Oracle
| View in TrackerStatus/Resolution/Reason: Closed/Withdrawn/
Reporter/Name(from Bugbase): Mary Jo Sminkey / Mary Jo Sminkey (Mary Jo Sminkey)
Created: 10/06/2010
Components: ORM Support
Versions: 9.0.1
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 1
Problem:
ORM does not properly create blob/clob fields in Oracle
Method:
When the ORM creates tables in Oracle, it is using RAW for a BLOB and LONG for CLOB. This is particularly problematic with clobs because Oracle will only allow a single LONG field in a table, while you can have multiple CLOBs, so if your table definition includes more than one clob, it throws errors due to trying to add two LONG fields instead. This behavior is occuring even though I have speciifcally told ORM to use the Oracle10g dialect, which supports CLOBs and BLOBs.
Result:
Problem with ORM generated clob/blob in Oracle
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3042380
External Customer Info:
External Company:
External Customer Name: Mary Jo Sminkey
External Customer Email: 054227314463B683992015D5
External Test Config: 10/06/2010Attachments:
Comments: