Help to restore databases after mysql reinstall

aaP_urbanbmobility

My mysql istallation acted up after server restart, i followed an advice from a contributor in this forum of deleting all databases to the recycle bin then reinstalling mysql. So i did this properly and mysql installed and updated from v5.7.41 to v5.7.44(don't know whether this can cause an issue). I restored my databases from the recycle bin successfully and can see all of them in /www/server/data. I can also successfully log into phpmyasdmin with database password, i can see all database table names on the left panel but not on the structure view on the right. Clicking on any table on the left throws the following sample error on mysql log:
"2024-11-01T15:29:15.772686Z 3076 [Warning] InnoDB: Cannot open table isp_db/ticketcomment from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue."
PLease assist to resolve the issue> Thanks

aaPanel_Kern

Hello, this is a wrong operation. Deleting the database and moving the recycle bin only marks for deletion, not moving the files. The actual files are still under /www/server/data
Have you ever backed up your data?

aaP_urbanbmobility

Thanks sir for your reply, I did not do a manual back up of my databases before re installing MySQL reason being mysql could not start up after server restart prompting me to reinstall it. I had downloaded/backed two bin files though(don't know whether these can help). I have all the database files available in the data folder.

aaPanel_Kern

Is it normal now?
If it is abnormal, please check the error log: cat /www/server/data/*.err|grep -i -C 10 error

aaP_urbanbmobility

aaP_arun.stellar12

I think you're facing an issue where MySQL is unable to open a table, even though the .frm file exists. This could be because of several reasons, especially after upgrading from MySQL 5.7.41 to 5.7.44. Here are the possible solutions:

Check Table Integrity: First, check the integrity of the affected tables. You can run the following command in MySQL to check and repair them:

CHECK TABLE isp_db.ticketcomment;

If any issues are found, use the REPAIR TABLE command to fix it.

Force Recovery: If the table still doesn’t open, try setting MySQL into force recovery mode. Add the following to your my.cnf or my.ini file under the [mysqld] section:

innodb_force_recovery = 1

This helps MySQL start without accessing corrupt InnoDB tables. Increase the recovery mode (1–6) until it starts. Remove the setting after recovery.

Check File Permissions: Ensure the files in /www/server/data/ have correct read/write permissions.
Review MySQL Logs: Check the error log for additional clues.
Restore from Backup: If you still can’t resolve the issue, consider restoring the table from a backup, if available.
Use other tool options: If the issue persists, there are many tool available such as Stellar Repair for MySQL because it can repair corrupted InnoDB tables, recover damaged .ibd and .frm files