View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004887 | SymmetricDS Pro | Bug | public | 2021-03-11 20:25 | 2021-03-30 19:47 |
Reporter | pmarzullo | Assigned To | pmarzullo | ||
Priority | normal | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.12.7 | ||||
Target Version | 3.12.8 | Fixed in Version | 3.12.8 | ||
Summary | 0004887: Oracle log miner stops processing rows when running into a DML statement that is not parseable | ||||
Description | When the Oracle log miner runs into a DML statement from the log mining result set (can't find table definition or the sql statement is empty), the processing of the current log mining result set stops. This then causes the log mining job to stop, waiting for the next run. When there are many invalid log mining statements, eventually the processing gets so far behind that the SCN that the log mining begins to work on is no longer in the redo logs, causing loss of change data capture. Change the processing to log the invalid statement, skip the invalid statement, and move on to the next one. | ||||
Tags | dialect: oracle, log miner | ||||
|
3.12.8 rc3 setup jar located here: https://www.jumpmind.com/downloads/symmetricds/preview/3.12/symmetric-pro-3.12.8.rc3-setup.jar |
Date Modified | Username | Field | Change |
---|---|---|---|
2021-03-11 20:25 | pmarzullo | New Issue | |
2021-03-11 20:25 | pmarzullo | Status | new => assigned |
2021-03-11 20:25 | pmarzullo | Assigned To | => pmarzullo |
2021-03-11 20:25 | pmarzullo | Tag Attached: dialect: oracle | |
2021-03-11 20:25 | pmarzullo | Tag Attached: log-miner | |
2021-03-11 20:31 | pmarzullo | Status | assigned => resolved |
2021-03-11 20:31 | pmarzullo | Resolution | open => fixed |
2021-03-11 20:31 | pmarzullo | Fixed in Version | => 3.12.8 |
2021-03-11 20:49 | pmarzullo | Note Added: 0001894 | |
2021-03-30 19:47 | admin | Status | resolved => closed |
2022-08-09 17:57 | admin | Tag Renamed | log-miner => log miner |