InnoDB: Attempted to open a previously opened tablespace

Question

I have been working on a problem for a few days now. Our local mediawiki page that sits on our box account, destroyed itself and we\'ve been working to get it online. Using

Answer 1

if someone has problems with any of their corrupt tables, this may be a possible solution to their problem, in my case I had the backup of my database so just delete the tables that are the files .ibd then restart MAMP PRO and mysql started correctly. A database backup must be taken into account. hope this helps someone and doesn't waste a lot of time. regards

Answer 2

To use the above (Nesar solution) in MAMP (version >= 4), you must first copy the my.cnf file that is inside MAMP/tmp/mysql to the MAMP/conf folder. Only then will it work.

Answer 3

I had the same problem. I tried all the solution others has proposed, and unfortunately nothing worked.

After spending hours on searching for the solution in Google I finally found this

1. Open my.ini (my.cnf on linux-based systems and Mac)
2. Look for [mysqld]
3. Just below [mysqld] insert innodb_force_recovery = 1
4. Start MySQL Service
5. Stop MySQL Service
6. Remove the line from my.ini (innodb_force_recovery = 1)
7. Start MySQL Service

Worked perfect in my case.

I hope this will solve your problem.

Answer 4

I got the same error. These are the steps I followed.

1. Took the backup of \xampp\mysql\data

2. Removed all the files and folders from data folder except mysql

3. Quit and started the XAMPP again.

4. Move the databases from data folder one by one.

Answer 5

try to rename /Applications/XAMPP/xamppfiles/var/mysql/ib_logfile0 to /Applications/XAMPP/xamppfiles/var/mysql/ib_logfile0.bkp

and /Applications/XAMPP/xamppfiles/var/mysql/ib_logfile1 to /Applications/XAMPP/xamppfiles/var/mysql/ib_logfile1.bkp

Answer 6

Another solution for the issue discribed above for MAMP Pro, as I found impossible to edit my.cnf properly :

When InnoDB is crashing, spot in the error message the DB that is causing trouble. Here it is phpmyadmin/pma__tracking so the table is the one with the pma_ extension.

Then go to /Library/Application Support/appsolute/MAMP PRO/db/mysql and remove the folder named after the problem causing DB.

Restart your MAMP server. Once you restarted with success, you can stop servers again, put back the DB folder where it belongs and start the servers again. Everything should be fine again.