Skip to content

Commit

Permalink
Merge pull request #3222 from EnterpriseDB/docs/mtk/jdbc-note
Browse files Browse the repository at this point in the history 
MTK: included info about moving file for EDB JDBC
  • Loading branch information
@drothery-edb
drothery-edb authored Oct 6, 2022
2 parents edfddc7 + 0bbe06f commit a5313c4
Show file tree
Hide file tree
Showing 2 changed files with 20 additions and 7 deletions.
12 changes: 12 additions & 0 deletions ...uct_docs/docs/migration_toolkit/55/05_installing_mtk/installing_jdbc_driver.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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/).
Expand All @@ -23,6 +24,17 @@ 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 `<mtk_install_dir>/lib` directory.

!!!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 `<mtk_install_dir>/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
```
!!!


15 changes: 8 additions & 7 deletions product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_553_rel_notes.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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. |

0 comments on commit a5313c4

Please sign in to comment.