Migration Assessment:
- Quickly determine how much effort an individual migration encompasses
- Inspect the cost for discrete database objects and identify outliers
Note: The figures given by the assessment are only a rough estimation.
We will continue to tweak and improve these values as we collect experience and introduce new technologies, such as a PL/SQL parser.- Quickly determine how much effort an individual migration encompasses
Migration Overview: List empty and non-empty schemas separately
Note: Empty schemas are now excluded per default
Migration Creation: Improve feedback for invalid connection strings
Migration Lifecycle:
- Defer the creation of functions after those of tables to allow for the use of the
%TYPEattribute - Enhance the migration log of the structure, integrity and logic stages to be on a par with those of the data stage
- Configure the
COPY FREEZEfunctionality introduced inv3.12.0for each individual table instead of the whole system. TheCORE_DATA_MIGRATOR_USE_COPY_FREEZEenvironment variable has subsequently been removed.
- Defer the creation of functions after those of tables to allow for the use of the
Miscellaneous: Rework the log output format and fidelity throughout the
corecontainer
- The Analyze step of the migration creation always shows
Jobsas pending - LOBs exceeding the maximum size of 500MB do not fail with an appropriate error message
- Setting the sidebar filter to
Indexdoes not include all indexes in the filter result - Usernames and passwords containing special characters cause the target connection check during migration creation to fail
- Deleting a migration after executing a stage fails with an unexpected error