View Issue Details

IDProjectCategoryView StatusLast Update
0006096SymmetricDSImprovementpublic2023-11-06 19:57
Reporterelong Assigned Toelong  
Status closedResolutionfixed 
Product Version3.15.0 
Target Version3.15.1Fixed in Version3.15.1 
Summary0006096: Contains big LOB check can be fooled by commas in data
DescriptionThe channel has a contains_big_lob setting that is usually disabled and allows the extractor to quickly extract data under the varchar limit. If data exceeds the varchar limit, it tries to detect it by counting the number of fields versus columns on the table. It does a quick comma count check, but it can be fooled if there are commas in the data. Wait for a Protocol Violation Exception to return on a batch (sql code -888) before doing extra processing of parsing the row data and checking data matches columns.

[DefaultDatabaseWriter] [client-2-dataloader-2] Failed to process update event in batch server-2299 on channel 'test1'.
Failed pk data was: "20"
Failed old data was: "20","fTuZqvknNchOBrkZdoPIX","O ","893429","2019-08-01 21:19:20.327"
org.jumpmind.exception.ParseException: The (mytest1) table's column count (6) does not match the data's column count (5)
    at org.jumpmind.symmetric.model.ProcessInfoDataWriter.write(
    at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$
    at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$
Tagsdialect: oracle, large objects


related to 0006095 resolvedelong Contains big LOB check can be fooled by commas in data 


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2023-11-06 19:57 elong New Issue
2023-11-06 19:57 elong Status new => assigned
2023-11-06 19:57 elong Assigned To => elong
2023-11-06 19:57 elong Tag Attached: dialect: oracle
2023-11-06 19:57 elong Tag Attached: large objects
2023-11-06 19:57 elong Issue generated from: 0006095
2023-11-06 19:57 elong Relationship added related to 0006095
2023-11-06 19:57 elong Status assigned => resolved
2023-11-06 19:57 elong Resolution open => fixed
2023-11-06 19:57 elong Fixed in Version => 3.15.1
2023-11-14 21:10 admin Status resolved => closed