Database does not start in 6.1.0 - 6.1.8 after upgrade from 6.0.x
Details
| Detail name | Value |
|---|---|
| Changelog Number | 9742 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.1.0 |
| Fix Versions | Exasol 7.0.0, Exasol 6.1.9, Exasol 6.2.5 |
| Resolution Date | 2020-03-20 |
Synopsis
When upgrading the database from 6.0.x to 6.1, the database does not start if the total number of columns in all its tables is large.
Details
Version 6.1 introduced some internal changes that require all tables to undergo some transformations upon the first database start.
If the total number of columns to be processed is too large (we reproduced the issue with 250,000 columns) then this automated process may fail with an out of memory event, preventing the database from starting.
Notes:
- Such a transformation does not take place when upgrading 6.1. -> 6.2
- Since the transformation affects the tables alone, the number of columns in views is irrelevant
- Direct upgrades from 6.0 to 6.2 or higher are not supported
Workaround
There is no workaround; the problem does no longer occur in versions containing the fix.
