View Issue Details

IDProjectCategoryView StatusLast Update
0005333SymmetricDSBugpublic2022-07-12 20:01
Reporterpmarzullo Assigned Topmarzullo  
Status closedResolutionfixed 
Product Version3.13.5 
Target Version3.13.6Fixed in Version3.13.6 
Summary0005333: Oracle log mining throwing exception when finding mismatched LOB record in log mining result set
DescriptionWhen a record has a LOB that is read in the log mining result set, the code is expecting that the next record should, if it is a lob write, should match the current owner (schema) and table.

It is possible that the next record, even though it is a lob write, is for a different owner/table.

We should log and move on for now.
Tagsdialect: oracle, log miner


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2022-06-10 14:19 pmarzullo New Issue
2022-06-10 14:19 pmarzullo Status new => assigned
2022-06-10 14:19 pmarzullo Assigned To => pmarzullo
2022-06-10 14:19 pmarzullo Tag Attached: dialect: oracle
2022-06-10 14:19 pmarzullo Tag Attached: log-miner
2022-06-10 14:26 pmarzullo Status assigned => resolved
2022-06-10 14:26 pmarzullo Resolution open => fixed
2022-06-10 14:26 pmarzullo Fixed in Version => 3.13.6
2022-07-12 20:01 admin Status resolved => closed
2022-08-09 17:57 admin Tag Renamed log-miner => log miner