Skip to content

Commit

Permalink
Merge pull request #6186 from EnterpriseDB/DOCS-1088-Tracking-55.10-work
Browse files Browse the repository at this point in the history 
MTK 55.10 release branch
  • Loading branch information
@gvasquezvargas
gvasquezvargas authored Nov 21, 2024
2 parents c3605de + 65bec2e commit c43b2b2
Show file tree
Hide file tree
Showing 4 changed files with 44 additions and 7 deletions.
4 changes: 2 additions & 2 deletions ...s/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,8 @@ title: "Supported platforms and databases"

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

- PostgreSQL versions 12, 13, 14, 15, and 16
- EDB Postgres Advanced Server versions 12, 13, 14, 15, and 16
- PostgreSQL versions 13, 14, 15, 16, and 17
- EDB Postgres Advanced Server versions 13, 14, 15, 16, and 17
- Oracle 11g
- Oracle 12c
- Oracle 18c
Expand Down
28 changes: 23 additions & 5 deletions product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ The command options that work with Migration Toolkit are grouped by their behavi
| [Import options](#import-options) | -sourcedbtype, -targetdbtype, -schemaOnly, -dataOnly |
| [Schema creation options](#schema-creation-options) | -dropSchema, -targetSchema |
| [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 |
| [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 |
| [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 |
| [Connection retry options](#connection-retry-options) | -connRetryCount, -connRetryInterval, -abortOnConnFailure |
| [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 |
| [Miscellaneous options](#miscellaneous-options) | -help, -logDir, -logFileCount, -logFileSize, -logBadSQL -verbose, -version |
Expand Down Expand Up @@ -450,21 +450,21 @@ The right side specifies a condition that must be true for each row migrated.

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

### `COUNTRIES=COUNTRY_ID<>'AR'`
`COUNTRIES=COUNTRY_ID<>'AR'`

This constraint applies to the COUNTRIES table.

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

### Example
Example:

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

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

`DEPARTMENTS=(DEPARTMENT_ID BETWEEN 10 AND 30)`

`-customColTypeMapping <column_list>`
### `-customColTypeMapping <column_list>`

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:

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

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

`-customColTypeMappingFile <property_file>`
### `-customColTypeMappingFile <property_file>`

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.

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

### `-mapVirtualToRegular`

Include the `-mapVirtualToRegular` option to migrate virtual, computed or generated columns in the source database to regular columns in the target database.

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.

For schema migrations, including the option results in all virtual columns in the source database being migrated to regular columns in the target database.

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.

For example, in:

```
./runMTK.sh -sourcedbtype sqlserver -targetdbtype enterprisedb -mapVirtualToRegular -allTables <schema_scope>
```

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.

## Connection retry options

Whenever there's a connection failure with the target database during a data migration, Migration Tookit attempts to reconnect to the
Expand Down
2 changes: 2 additions & 0 deletions product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ title: "Release notes"
redirects:
- ../01_whats_new/
navigation:
- mtk_55100_rel_notes
- mtk_5590_rel_notes
- mtk_5580_rel_notes
- mtk_5570_rel_notes
Expand All @@ -23,6 +24,7 @@ The Migration Toolkit documentation describes the latest version of Migration To

| Version | Release Date |
|---------------------------------|--------------|
| [55.10.0](mtk_55100_rel_notes) | 21 Nov 2024 |
| [55.9.0](mtk_5590_rel_notes) | 21 Aug 2024 |
| [55.8.0](mtk_5580_rel_notes) | 16 May 2024 |
| [55.7.0](mtk_5570_rel_notes) | 13 Dec 2023 |
Expand Down
17 changes: 17 additions & 0 deletions product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "Migration Toolkit 55.10.0 release notes"
navTitle: Version 55.10.0
---

Released: 21 Nov 2024

New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.10.0 include:

| Type | Description | Ticket |
|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
| Enhancement | Migration Toolkit now supports PostgreSQL version 17 and EDB Postgres Advanced Server version 17 both as a source and target database. | |
| 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 |
| 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 |
| 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. | |
| 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. | |
| Bug&nbsp;fix | Fixed an issue where the indexes are skipped from migration when multiple tables are selected for a source MySQL database. | |

0 comments on commit c43b2b2

Please sign in to comment.