Wrong results on single node systems when joining replicated tables with rows marked for deletion
Details
| Detail name | Value |
|---|---|
| Changelog Number | 7001 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.10 |
| Fix Versions | Exasol 6.0.13 |
| Resolution Date | 2018-11-08 |
In EXASOL-2248 table replication costs have been reduced by accessing directly the data of the un-replicated table instance.
This feature introduced a bug producing wrong results when joining replicated tables with the following properties:
- single node system
- base table has deleted marked rows
- replicated table existed before 6.0.10 and had indices
When upgrading to 6.0.10 the existing indices on replicated tables became inconsistent with the referenced base table data (bug).
Fix
When upgrading to the latest version all replicated table instances will be dropped automatically.
Workaround
By reorganizing the database the inconsistent indices on replicated tables can be repaired. The ENFORCE keyword is necessary!
REORGANIZE DATABASE ENFORCE;
This statement can take minutes up to an hour.
