Migrate necessary DB objects on a schema by schema basis
Details
| Detail name | Value |
|---|---|
| Changelog Number | 22402 |
| Type | Improvement |
| Status | Resolved |
| Fix Versions | Exasol 8.29.10, Exasol 2025.1.0 |
| Resolution Date | 2025-05-15 |
Background
In some situations, like database update, database enlargement etc. database needs to “migrate” some objects. For example, migration process might include change of internal structures and data redistribution.
Earlier, whenever the database objects needed to be migrated, Exasol database migrated all the objects in the database, and afterwards a commit was performed to make the changes persistent. In case too many objects needed to be accessed (in particular schemas and schema objects) too much memory may have been needed and the system may have run into an out of memory scenario, which prevented the database from starting.
Improvement
If the database objects need to be migrated (tables/schemas/views/scripts), then after each migrated schema a commit is performed. This avoids the out of memory.
