Backup procedure in Plesk ends with warning: Unable to make database dump. Got error 194 Tablespace is missing for a table

Symptoms

• Plesk backup finishes with the warning:
  

  CONFIG_TEXT: Warning: Database "wp_databasename"
  Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2: mysqldump: Got error: 1030: "Got error 194 "Tablespace is missing for a table" from storage engine InnoDB" when using LOCK TABLES

• The following errors are found in /var/log/mysq/error.log:

  CONFIG_TEXT: 2022-06-29 3:16:52 255 [ERROR] InnoDB: Failed to find tablespace for table `wp_databasename`.`wphtq4_posts` in the cache. Attempting to load the tablespace with space id 3818
  2022-06-29 3:16:52 255 [ERROR] InnoDB: Operating system error number 2 in a file operation.
  2022-06-29 3:16:52 255 [ERROR] InnoDB: The error means the system cannot find the path specified.
  2022-06-29 3:16:52 255 [ERROR] InnoDB: Cannot open datafile for read-only: './wp_databasename/wphtq4_posts.ibd' OS error: 71
  2022-06-29 3:16:52 255 [ERROR] InnoDB: Operating system error number 2 in a file operation.
  2022-06-29 3:16:52 255 [ERROR] InnoDB: The error means the system cannot find the path specified.
  2022-06-29 3:16:52 255 [ERROR] InnoDB: Could not find a valid tablespace file for ``wp_databasename`.`wphtq4_posts``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.

• The file error message is missing on the server:

  # stat /var/lib/mysql/wp_databasename/wphtq4_posts.ibd
  stat: cannot stat '/var/lib/mysql/wp_databasename/wphtq4_posts.ibd': No such file or directory

Cause

Database corruption.

Resolution

Restore the database in question from a backup by following the instructions from this article.

If the database is not needed, remove it.