Plesk update and APS application installation fail: No ODBC MySQL mysql drivers found, trying /usr/lib64/libmyodbc5a.so

Symptoms

• Application installation fails with in the file /var/log/plesk/panel.log:

  CONFIG_TEXT: [2019-05-06 22:45:45.606] ERR [panel] Exception: std::bad_alloc
  file: /usr/share/aps_php/aps_php.php
  line: 7173
  code: 0

• Unable to access WordPress Toolkit page in Plesk, a blank page or the error below is displayed:

  CONFIG_TEXT: Server Error
  502
  Bad Gateway

• Plesk update fails with the following error in the file /var/log/plesk/autoinstaller3.log:

  CONFIG_TEXT: ERROR while trying to No ODBC MySQL mysql drivers found, trying /usr/lib64/libmyodbc5.so /usr/lib64/libmyodbc5a.so

• Installation of any application in Domains > example.com > Applications fails with one of the following error messages:

  CONFIG_TEXT: ODBC error #01000: [unixODBC][Driver Manager]Can't open lib '/usr/lib64/libmyodbc5.so' : file not found

  CONFIG_TEXT: Error: The following error has occurred during the download of application:
  ODBC error #23000: [MySQL][ODBC 8.0(w) Driver][mysqld-5.6.44]Duplicate entry '4-Prestashop' for key 'IX_aps_package_resource_configuration'

• Unable to create subscription, domain, or subdomain:

  PLESK_INFO: Server Error
  502
  Bad Gateway

• At the same time below information can be found in the file /var/log/sw-cp-server/sw-engine.log:

  CONFIG_TEXT: [01-May-2019 01:14:15] WARNING: [pool plesk] child 9650 exited on signal 6 (SIGABRT) after 26.178925 seconds from start
  [01-May-2019 01:15:00] WARNING: [pool plesk] child 10391 exited on signal 11 (SIGSEGV) after 4.845059 seconds from start

• MySQL was upgraded recently.

• MySQL Community edition repositories are enabled:

  # yum repolist enabled | grep mysql
  mysql-connectors-community mysql-connectors-community 83
  mysql-tools-community MySQL Tools Community 74
  mysql56-community MySQL 5.6 Community Server 493

• ODBC connector has version like 8.0.x. For example:

  # rpm -qa | grep ^mysql-connector
  mysql-connector-odbc-8.0.13-1.el6.x86_64

Cause

Resolution

Workaround

If update is not possible for some reason you may try the following