Solving the 'MySQL No Database Selected' Error in Ignition Gateway

When configuring or upgrading your MySQL database to version 8.0, you may encounter an issue where the connection faults and the Ignition gateway posts an error in the logs stating that no database has been selected. This problem can be resolved by updating the JDBC driver for MySQL.

To begin, open your Ignition Gateway Webpage interface and navigate to the JDBC drivers page. Download the JDBC driver (version 8.0.11 at the time of writing) from the official Oracle website. Extract the contents of the ZIP archive and save them in a directory that is easily accessible.

In the drop-down list for Select Operating System, select Platform Independent and download the ZIP Archive. You can also retrieve the latest JDBC driver by visiting the following link: 'Download the latest JDBC driver for MySQL'.

The solution to this problem lies in updating the MySQL JDBC driver to the latest version provided by Oracle. This change would cause the previous driver to not function correctly on a new database version, leading to the 'MySQL No Database Selected' error.

Ignition, by default, ships with JDBC drivers for major databases; however, there may be cases where a new database version requires an updated JDBC driver to be released by the developer of the database. In this instance, changes introduced in MySQL 8.0 broke backward compatibility with the bundled JDBC driver, leading to connection faults and errors.

To resolve this issue, update the JDBC driver for MySQL, change the Classname value, and set Extra Connection Properties accordingly. By doing so, you will be able to connect to your MySQL database successfully.

Background Information:

When configuring or upgrading your MySQL database to version 8.0, the connection would get faulted and the Ignition gateway would post the following error(s) in the logs: .SQLNestedException: Cannot create PoolableConnectionFactory (Unable to load authentication plugin 'caching_sha2_password'.) .SQLNestedException: Cannot create PoolableConnectionFactory (: cannot be cast to )

It is important to note that this issue has been fixed in version 7.9.9 of Ignition, and any clean installations of that version will contain the changes referenced above by default. However, on versions prior to Ignition 7.9.9, you will continue to see an error in the Database Query Browser that it fails to list the table names with the changes made above.

Mysql no database selected