There's a slim but existing chance that the database is not broken and this is a false positive. If you are on Windows this is the case. Please do note that the real problem is that you are using an uppercase letter in the database prefix (dknc8N
9_) which causes all sorts of trouble on Windows due to a MySQL quirk (I won't call it a bug because they have documented it exists and why it can't be fixed).
Please note that the underlying MySQL issue will prevent you from restoring your site using a different database prefix
. You should also be getting a warning linking you to the Q106 warning page on our site
. Please read that page to get more insight on what's going on.
In order to fix it you would need to take a backup of your site and restore it with the same
database prefix on a Linux or macOS server. Then you'd have to back it up from the Linux/macOS server. Then you'd need to remove all database tables from your Windows server. Finally, you'd need to restore the backup you took from the Linux/macOS server with a new, all lowercase, prefix such as dknc8n9_
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!