Database fails to start after cluster enlargement due to exceeded schema raw size limits
Details
| Detail name | Value |
|---|---|
| Changelog Number | 13056 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.2.15 |
| Fix Versions | Exasol 8.0.0, Exasol 7.1.2, Exasol 6.2.18, Exasol 7.0.14 |
| Resolution Date | 2021-10-20 |
Description
The database does not start after a cluster enlargement if the raw_size_limit is exceeded.
Workaround
Temporarily increase the raw_size_limit to ensure it is not exceeded prior to a cluster enlargement.
The following query shows the schemas with exceeded raw_size_limit:
SELECT OBJECT_NAME, RAW_OBJECT_SIZE, RAW_OBJECT_SIZE_LIMIT FROM EXA_DBA_OBJECT_SIZES WHERE OBJECT_TYPE='SCHEMA' AND RAW_OBJECT_SIZE_LIMIT < RAW_OBJECT_SIZE;
Fix
The database does start after a cluster enlargement independent of the raw_size_limit.
