Partitioned tables unusable after updating from 6.2 to 7.0.0
Details
| Detail name | Value |
|---|---|
| Changelog Number | 10785 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.0.0 |
| Fix Versions | Exasol 7.0.1 |
| Resolution Date | 2020-09-23 |
Description
When upgrading from 6.2.x to 7.0.0, tables that contained a PARTITION BY clause are not migrated correctly. This manifests by query crashes whenever metadata of those partitioned tables are accessed. When querying metadata information (including the DESCRIBE command and selecting system tables like EXA_ALL_TABLES, EXA_ALL_COLUMNS), you will receive the following error:
Successfully reconnected after internal server error, transaction was rolled back.
The tables themselves are not corrupted and their data is intact, they are just inaccessible.
Workaround
To fix this error, you can contact Exasol support and they can provide you with a patch.
To install the patch, you can follow the instructions in our documentation: https://docs.exasol.com/administration/on-premise/upgrade/updates.htm
Fix
Reading metadata of partitioned tables will no longer return an internal server error. We recommend updating to 7.0.1 directly as soon as it is available.
