View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006174 | SymmetricDS | Improvement | public | 2024-01-03 17:12 | 2024-04-10 17:54 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.15.0 | ||||
| Target Version | 3.15.3 | Fixed in Version | 3.15.3 | ||
| Summary | 0006174: Could not find trigger history, causes error of had X columns but expected Y | ||||
| Description | When extracting a batch, if a trigger history cannot be found, it will look up and use the first active trigger history for the table. If the table was recently altered to include more or fewer columns, then the trigger history won't match the data, which leads to the following log messages and error: WARN [node-1] [DataService] [node-1-dataextractor-1] Could not find trigger history 377 for table mytable for data_id 175848. Using trigger hist 1206 instead. WARN [node-1] [DataExtractorService] node-1-push-default-1] The batch server01-10670 appears corrupt in staging, so removing it. (The extracted row for table mytable had 14 columns but expected 17. Corrupted row for data ID 175848 Instead, it should look up any active or non-active trigger history with a column count and primary key count that matches the data row. If there isn't a matching one, then there is no choice left but to use the current active trigger history. | ||||
| Tags | extract | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-01-03 17:12 | elong | New Issue | |
| 2024-01-03 17:12 | elong | Status | new => assigned |
| 2024-01-03 17:12 | elong | Assigned To | => elong |
| 2024-01-03 17:12 | elong | Tag Attached: extract | |
| 2024-01-03 17:12 | elong | Issue generated from: 0006173 | |
| 2024-01-03 17:12 | elong | Relationship added | related to 0006173 |
| 2024-01-03 17:12 | elong | Status | assigned => resolved |
| 2024-01-03 17:12 | elong | Resolution | open => fixed |
| 2024-01-03 17:12 | elong | Fixed in Version | => 3.15.3 |
| 2024-02-05 18:58 | admin | Status | resolved => closed |
| 2024-04-10 17:54 | jvanmeter | Relationship added | related to 0004617 |