[DERBY-2864] LOB import unexpectedly succeeds on corrupt data

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.3.1.4
• Component/s: SQL
• Labels: derby_triage10_5_2
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 22/Jun/07 18:12
• Updated: 15/Feb/11 21:09

Description

I exported a lob-bearing table using the SYSCS_UTIL.SYSCS_EXPORT_TABLE_LOBS_TO_EXTFILE procedure. Then I edited the export file to change the length of one of the lobs to an absurdly large number (500K). Then I ran SYSCS_UTIL.SYSCS_IMPORT_DATA_LOBS_FROM_EXTFILE. I expected this command would fail while trying to read beyond the end of the lob file. However, it succeeded.

I think that the import should fail, and the user should see an exception which identifies the line number and column number holding the corrupt lob pointer. I will attach a test case.

Issue Links

• blocks: DERBY-378 support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,