From 8e191b3cf843e539e682007d961ef10735504fba Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 6 Oct 2022 10:09:41 -0400 Subject: [PATCH 1/4] MTK: included info about moving file for EDB JDBC --- .../55/05_installing_mtk/installing_jdbc_driver.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx index a3cca1d681b..ce3d33af8c5 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx @@ -5,6 +5,7 @@ title: "Installing a JDBC driver" Migration Toolkit requires Java version 1.8.0 or later. +## Choosing a driver Which JDBC driver you use depends on the what database you are migrating from or to: - If you're migrating to or from EDB Postgres Advanced Server, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). @@ -23,6 +24,14 @@ Which JDBC driver you use depends on the what database you are migrating from or !!! Note The open source jTDS driver also supports older versions of Microsoft SQL Server (version 2012 and earlier) and may be used with Migration Toolkit. The Microsoft provided JDBC driver for SQL Server is recommended for the newer versions of SQL Server supported by Migration Toolkit. +## Adding the driver to `lib` After downloading the driver, move the driver file into the `/lib` directory. +!!! Note +For the case of the EDB JDBC driver, if it is installed prior to installing Migration Toolkit it should not be necessary to place a copy of it in the /lib directory as a symbolic link to the edb-jdbc18.jar file is created during installation of Migration Toolkit. After installing Migration Toolkit, you can verify whether the symbolic link exists by executing the following command: + +``` +ls -l /usr/edb/migrationtoolkit/lib/edb-jdbc18.jar +``` + From ab1987dbd69e850c62ac26c394ea8e0fa76ca51b Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 6 Oct 2022 11:15:00 -0400 Subject: [PATCH 2/4] Added SQL deprecated to rel notes Also did more formatting on new JDBC driver --- .../05_installing_mtk/installing_jdbc_driver.mdx | 6 ++++-- .../55/mtk_rel_notes/mtk_553_rel_notes.mdx | 15 ++++++++------- 2 files changed, 12 insertions(+), 9 deletions(-) diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx index ce3d33af8c5..91d8bb4acbf 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx @@ -27,8 +27,10 @@ Which JDBC driver you use depends on the what database you are migrating from or ## Adding the driver to `lib` After downloading the driver, move the driver file into the `/lib` directory. -!!! Note -For the case of the EDB JDBC driver, if it is installed prior to installing Migration Toolkit it should not be necessary to place a copy of it in the /lib directory as a symbolic link to the edb-jdbc18.jar file is created during installation of Migration Toolkit. After installing Migration Toolkit, you can verify whether the symbolic link exists by executing the following command: +!!!note "For EDB JDBC driver" +If the EDB JDBC driver is installed prior to installing Migration Toolkit it should not be necessary to place a copy of it in the `/lib` directory. A symbolic link to the edb-jdbc18.jar file is created during installation of Migration Toolkit. + +After installing Migration Toolkit, you can verify whether the symbolic link exists by executing the following command: ``` ls -l /usr/edb/migrationtoolkit/lib/edb-jdbc18.jar diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx index 14e039e0623..a316d8b729d 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx @@ -4,10 +4,11 @@ title: "Version 55.3.0" New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.3 include: -| Type | Description | -| ------------ |------------ | -| Enhancement | Migration Toolkit is now certified to work with the Microsoft provided SQL Server JDBC driver version 10.2. Although the open source jTDS driver can still be used for connections to Microsoft SQL Server with Migration Toolkit, it is recommended that the Microsoft provided SQL Server JDBC driver be used instead as it provides support for the more recent versions of SQL Server. | -| Enhancement | Migration Toolkit is now certified to work on the Debian 11 platform. | -| Security Fix | Migration Toolkit has been certified with the latest EDB JDBC driver version 42.5.0.1 and PostgreSQL community JDBC driver version 42.5.0 that contain the security fix for [CVE-2022-31197](https://nvd.nist.gov/vuln/detail/CVE-2022-31197). | -| Security Fix | Migration Toolkit has been certified to work with the MySQL JDBC driver version 8.0.30 that contains the security fix for [CVE-2022-21363](https://nvd.nist.gov/vuln/detail/CVE-2022-21363). References to the MySQL JDBC driver in the Migration Toolkit document have been correspondingly updated. | -| Bug Fix | Fixed an issue where an Oracle table migration to EPAS fails when it contains a virtual column. [Support Ticket # 82718] | +| Type | Description | +| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Enhancement | Migration Toolkit is now certified to work with the Microsoft provided SQL Server JDBC driver version 10.2. Although the open source jTDS driver can still be used for connections to Microsoft SQL Server with Migration Toolkit, it is recommended that the Microsoft provided SQL Server JDBC driver be used instead as it provides support for the more recent versions of SQL Server. | +| Enhancement | Migration Toolkit is now certified to work on the Debian 11 platform. | +| Security Fix | Migration Toolkit has been certified with the latest EDB JDBC driver version 42.5.0.1 and PostgreSQL community JDBC driver version 42.5.0 that contain the security fix for [CVE-2022-31197](https://nvd.nist.gov/vuln/detail/CVE-2022-31197). | +| Security Fix | Migration Toolkit has been certified to work with the MySQL JDBC driver version 8.0.30 that contains the security fix for [CVE-2022-21363](https://nvd.nist.gov/vuln/detail/CVE-2022-21363). References to the MySQL JDBC driver in the Migration Toolkit document have been correspondingly updated. | +| Bug Fix | Fixed an issue where an Oracle table migration to EPAS fails when it contains a virtual column. [Support Ticket # 82718] | +| Other | Removed support of Microsoft SQL Server 2008 and SQL Server Server 2012 for use with Migration Toolkit since these versions are no longer supported by Microsoft. These versions had previously been tested and certified for use with Migration Toolkit. Although they may continue to work with Migration Toolkit, EDB is no longer performing ongoing verification of them. | \ No newline at end of file From 44e0beb08f8862629e844a585f2a19473870524e Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 6 Oct 2022 11:37:16 -0400 Subject: [PATCH 3/4] Closing note --- .../55/05_installing_mtk/installing_jdbc_driver.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx index 91d8bb4acbf..bae23f20525 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx @@ -35,5 +35,6 @@ After installing Migration Toolkit, you can verify whether the symbolic link exi ``` ls -l /usr/edb/migrationtoolkit/lib/edb-jdbc18.jar ``` +!!! From 0bbe06f93cc371e31e881be262b3104e567e7f25 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 6 Oct 2022 11:42:01 -0400 Subject: [PATCH 4/4] added missing article --- .../55/05_installing_mtk/installing_jdbc_driver.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx index bae23f20525..b93c78e30cc 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx @@ -27,7 +27,7 @@ Which JDBC driver you use depends on the what database you are migrating from or ## Adding the driver to `lib` After downloading the driver, move the driver file into the `/lib` directory. -!!!note "For EDB JDBC driver" +!!!note "For the EDB JDBC driver" If the EDB JDBC driver is installed prior to installing Migration Toolkit it should not be necessary to place a copy of it in the `/lib` directory. A symbolic link to the edb-jdbc18.jar file is created during installation of Migration Toolkit. After installing Migration Toolkit, you can verify whether the symbolic link exists by executing the following command: