From bd3de0ac8b7cf6deaeeb900fb1a8aab8a752c8bf Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Thu, 23 May 2024 15:50:04 -0400 Subject: [PATCH 1/2] Edits to Migration Toolkit PR5658 --- product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx b/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx index 3d31145e9a3..01a579f42d3 100644 --- a/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx +++ b/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx @@ -259,19 +259,18 @@ To correct the problem, specify `-fetchSize 1` as a command-line argument when y ### Incorrect timestamps and Daylight Saving Time -When migrating from SQL Server to PostgreSQL using the MSSQL JDBC driver there may be no errors observed. If the source database contains rows with timestamp values which are within a range of time when Daylight Savings Time was in effect, they will be migrated to the target database with the wrong timestamps. +When migrating from SQL Server to PostgreSQL using the MSSQL JDBC driver, the migration may error without reporting any errors. However, if the source database contains rows with timestamp values that are within a range of time when Daylight Savings Time was in effect, those rows will be migrated to the target database with the wrong timestamps. -To resolve this issue you can update the `runMTK.sh` file and provide the option `-Duser.timezone=GMT`. This will be in operation then when running the toolkit, +To resolve this issue, update the `runMTK.sh` file, and provide the option `-Duser.timezone=GMT`. This option will then be in effect when you run the toolkit. -For example, given the original line: +For example, suppose this is the original line: ```text runJREApplication $JAVA_HEAP_SIZE -Dprop=$base/etc/toolkit.properties -cp $base/bin/edb-migrationtoolkit.jar:$base/lib/* com.edb.MigrationToolkit "$@" ``` -This should be updated with the `-Duser.timezone=GMT` inserted before the `-cp` option: +Update this line by inserting `-Duser.timezone=GMT` before the `-cp` option: ```text runJREApplication $JAVA_HEAP_SIZE -Dprop=$base/etc/toolkit.properties -Duser.timezone=GMT -cp $base/bin/edb-migrationtoolkit.jar:$base/lib/* com.edb.MigrationToolkit "$@" ``` - From 38f996939d38c3c9812aecdacc1f7bfdd4ecbf8b Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Mon, 3 Jun 2024 12:14:53 +0200 Subject: [PATCH 2/2] timestamp error wording Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> --- product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx b/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx index 01a579f42d3..5067097113e 100644 --- a/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx +++ b/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx @@ -259,7 +259,7 @@ To correct the problem, specify `-fetchSize 1` as a command-line argument when y ### Incorrect timestamps and Daylight Saving Time -When migrating from SQL Server to PostgreSQL using the MSSQL JDBC driver, the migration may error without reporting any errors. However, if the source database contains rows with timestamp values that are within a range of time when Daylight Savings Time was in effect, those rows will be migrated to the target database with the wrong timestamps. +When migrating from SQL Server to PostgreSQL using the MSSQL JDBC driver, an error in the migration of timestamps may occur that is not reported. Specifically, if the source database contains rows with timestamp values that are within a range of time when Daylight Savings Time was in effect, those rows will be migrated to the target database with the wrong timestamps. To resolve this issue, update the `runMTK.sh` file, and provide the option `-Duser.timezone=GMT`. This option will then be in effect when you run the toolkit.