View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005333 | SymmetricDS | Bug | public | 2022-06-10 14:19 | 2022-07-12 20:01 |
| Reporter | pmarzullo | Assigned To | pmarzullo | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.13.5 | ||||
| Target Version | 3.13.6 | Fixed in Version | 3.13.6 | ||
| Summary | 0005333: Oracle log mining throwing exception when finding mismatched LOB record in log mining result set | ||||
| Description | When 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. | ||||
| Tags | dialect: oracle, log miner | ||||
| 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 |