Skip to content

Commit c43b2b2

Browse files
gvasquezvargasgvasquezvargas
authored
Merge pull request #6186 from EnterpriseDB/DOCS-1088-Tracking-55.10-work
MTK 55.10 release branch
2 parents c3605de + 65bec2e commit c43b2b2

File tree

4 files changed

+44
-7
lines changed

4 files changed

+44
-7
lines changed

‎product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@ title: "Supported platforms and databases"
99

1010
You can use the following database product versions with Migration Toolkit:
1111

12-
- PostgreSQL versions 12, 13, 14, 15, and 16
13-
- EDB Postgres Advanced Server versions 12, 13, 14, 15, and 16
12+
- PostgreSQL versions 13, 14, 15, 16, and 17
13+
- EDB Postgres Advanced Server versions 13, 14, 15, 16, and 17
1414
- Oracle 11g
1515
- Oracle 12c
1616
- Oracle 18c

‎product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx

Lines changed: 23 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ The command options that work with Migration Toolkit are grouped by their behavi
2323
| [Import options](#import-options) | -sourcedbtype, -targetdbtype, -schemaOnly, -dataOnly |
2424
| [Schema creation options](#schema-creation-options) | -dropSchema, -targetSchema |
2525
| [Schema object selection options](#schema-object-selection-options) | -allTables, -tables, -excludeTables,<br /><br />-constraints, -ignoreCheckConstFilter,<br /><br />-skipCKConst, -skipFKConst,<br /><br />-skipColDefaultClause,<br /><br />-indexes, -triggers,<br /><br />-allViews, -views, -excludeViews,<br /><br />-allSequences, -sequences, -excludeSequences,<br /><br />-allProcs, -procs, -excludeProcs,<br /><br />-allFuncs, -funcs, -excludeFuncs,<br /><br />-checkFunctionBodies,<br /><br />-allPackages, -packages, -excludePackages,<br /><br />-allDomains,<br /><br />-allQueues, -queues, -excludeQueues<br /><br />-allRules,<br /><br />-allgroups, -groups |
26-
| [Migration options](#migration-options) | -truncLoad, -enableConstBeforeDataLoad,<br /><br />-retryCount, -safeMode, -fastCopy,<br /><br />-analyze, vacuumAnalyze, -replaceNullChar,<br /><br />-copyDelimiter, -batchSize,<br /><br />-cpBatchSize, -lobBatchSize,<br /><br />-fetchSize, -filterProp<br /><br />-customColTypeMapping, -customColTypeMappingFile |
26+
| [Migration options](#migration-options) | -truncLoad, -enableConstBeforeDataLoad,<br /><br />-retryCount, -safeMode, -fastCopy,<br /><br />-analyze, vacuumAnalyze, -replaceNullChar,<br /><br />-copyDelimiter, -batchSize,<br /><br />-cpBatchSize, -lobBatchSize,<br /><br />-fetchSize, -filterProp<br /><br />-customColTypeMapping, -customColTypeMappingFile<br /><br />-mapVirtualToRegular |
2727
| [Connection retry options](#connection-retry-options) | -connRetryCount, -connRetryInterval, -abortOnConnFailure |
2828
| [Oracle-specific options](#oracle-specific-options) | -allUsers, -users,<br /><br />-allProfiles, -profiles,<br /><br />-importPartitionAsTable,<br /><br />-objectTypes,<br /><br />-copyViaDBLinkOra, -allDBLinks<br /><br />-allSynonyms, -allPublicSynonyms, -excludeSynonyms,<br /><br />-allPrivateSynonyms, -useOraCase,<br /><br />-skipUserSchemaCreation |
2929
| [Miscellaneous options](#miscellaneous-options) | -help, -logDir, -logFileCount, -logFileSize, -logBadSQL -verbose, -version |
@@ -450,21 +450,21 @@ The right side specifies a condition that must be true for each row migrated.
450450

451451
For example, this code migrates only those countries with a `COUNTRY_ID` value that isn't equal to `AR`:
452452

453-
### `COUNTRIES=COUNTRY_ID<>'AR'`
453+
`COUNTRIES=COUNTRY_ID<>'AR'`
454454

455455
This constraint applies to the COUNTRIES table.
456456

457457
You can also specify conditions for multiple tables. However, the condition for each table must be on a new line in the property file.
458458

459-
### Example
459+
Example:
460460

461461
The following entries in the properties file migrate only the relevant data from EMPLOYEES and the DEPARTMENTS tables:
462462

463463
`EMPLOYEES=(LAST_NAME IN ('Grant','Weiss') AND PHONE_NUMBER LIKE '650%')`
464464

465465
`DEPARTMENTS=(DEPARTMENT_ID BETWEEN 10 AND 30)`
466466

467-
`-customColTypeMapping <column_list>`
467+
### `-customColTypeMapping <column_list>`
468468

469469
Use custom type mapping to change the data type of migrated columns. The left side of each pair specifies the columns with a regular expression. The right side of each pair names the data type for that column to assume. You can include multiple pairs in a semi-colon-separated list for `<column_list>`. For example, to map any column whose name ends in `ID` to type `INTEGER`, use the following custom mapping entry:
470470

@@ -482,12 +482,30 @@ On Windows, use `'\.'` to represent the `'.'` character:
482482

483483
Alternatively, you can include multiple custom type mappings in a `<property_file>`:
484484

485-
`-customColTypeMappingFile <property_file>`
485+
### `-customColTypeMappingFile <property_file>`
486486

487487
Specify each entry in the file on a separate line in a key=value pair. The left side of each pair selects the columns with a regular expression. The right side of each pair names the data type for that column to assume. When used in the `<property_file>`, the `'\\'` characters act as an escape string in any operating system.
488488

489489
<div id="parallel_loading" class="registered_link"></div>
490490

491+
### `-mapVirtualToRegular`
492+
493+
Include the `-mapVirtualToRegular` option to migrate virtual, computed or generated columns in the source database to regular columns in the target database.
494+
495+
Turning virtual columns to regular columns is helpful when the expression used to compute the values in the source database column is not supported in the target database or cannot be translated into an expression supported by the target database. With this option, you can still migrate the column's values to the target, but the values will no longer be computed dynamically, as they are stored in a regular column.
496+
497+
For schema migrations, including the option results in all virtual columns in the source database being migrated to regular columns in the target database.
498+
499+
For data migrations, including the option extracts the computed values from all computed columns in the source database and inserts those values into regular columns in the target database.
500+
501+
For example, in:
502+
503+
```
504+
./runMTK.sh -sourcedbtype sqlserver -targetdbtype enterprisedb -mapVirtualToRegular -allTables <schema_scope>
505+
```
506+
507+
A column called `FullName` that is computed from other two columns called `FirstName` and `LastName` in the source database, is migrated as a regular column called `FullName` in the target database. In the target, this column is no longer dynamically generated, but displays the `FullName` value the source database had at the time the migration was performed.
508+
491509
## Connection retry options
492510

493511
Whenever there's a connection failure with the target database during a data migration, Migration Tookit attempts to reconnect to the

‎product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: "Release notes"
33
redirects:
44
- ../01_whats_new/
55
navigation:
6+
- mtk_55100_rel_notes
67
- mtk_5590_rel_notes
78
- mtk_5580_rel_notes
89
- mtk_5570_rel_notes
@@ -23,6 +24,7 @@ The Migration Toolkit documentation describes the latest version of Migration To
2324

2425
| Version | Release Date |
2526
|---------------------------------|--------------|
27+
| [55.10.0](mtk_55100_rel_notes) | 21 Nov 2024 |
2628
| [55.9.0](mtk_5590_rel_notes) | 21 Aug 2024 |
2729
| [55.8.0](mtk_5580_rel_notes) | 16 May 2024 |
2830
| [55.7.0](mtk_5570_rel_notes) | 13 Dec 2023 |

‎product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: "Migration Toolkit 55.10.0 release notes"
3+
navTitle: Version 55.10.0
4+
---
5+
6+
Released: 21 Nov 2024
7+
8+
New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.10.0 include:
9+
10+
| Type | Description | Ticket |
11+
|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
12+
| Enhancement | Migration Toolkit now supports PostgreSQL version 17 and EDB Postgres Advanced Server version 17 both as a source and target database. | |
13+
| Enhancement | Improved the handling and consistency in migrating virtual columns across different source and target database combinations. <br/> You can now choose whether to migrate virtual columns as virtual columns or map them to regular columns in the target. See [mapVirtualToRegular](../07_invoking_mtk/08_mtk_command_options/#-mapvirtualtoregular) for more information. | #38897 |
14+
| Bug&nbsp;fix | Fixed an issue that caused synonyms from all source schemas to be migrated even when only one schema was selected for migration. | #41178 |
15+
| Bug&nbsp;fix | Fixed an issue where the MySQL column type `BIGINT AUTO_INCREMENT` is not mapped to the `BIGSERIAL` column type in the target PostgreSQL/EDB Postgres Advanced Server table. | |
16+
| Bug&nbsp;fix | Fixed the issue where migration fails in parallel mode for a table with a primary key based on the float data type. | |
17+
| Bug&nbsp;fix | Fixed an issue where the indexes are skipped from migration when multiple tables are selected for a source MySQL database. | |

0 commit comments

Comments
 (0)