Improve company productivity with a Business Account.Sign Up

x
?
Solved

MySQL: Attempted to open a previously opened tablespace

Posted on 2013-11-19
3
Medium Priority
?
4,870 Views
Last Modified: 2013-11-21
Hi Experts,

I'm having issues starting the MySql service under XAMPP 1.8.3:

MySql log error:

2013-11-19 09:10:54 5224 InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db_binder_htl/tbladdress uses space ID: 1 at filepath: .\db_binder_htl\tbladdress.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

I had this issue before and solved it by moving the files within xampp\mysql\data folder and letting MySQL rebuild them, but now it is back.

I need a permanent solution. Any suggestions?

Thanks
0
Comment
Question by:rmartes
3 Comments
 
LVL 82

Expert Comment

by:arnold
ID: 39661587
Did your system crash, or cold powered off (loss of power)?

What your storage is like

Depending on what led to this issue and whether you are ok with a possible data loss, adding an innodb_force_recovery=1 in /etc/my.cnf will let mysql do its thing and start working (with possible data loss)

Storage type/configuration might be what under certain circumstances is susceptible to this issue.
Filesystem type.
0
 
LVL 1

Accepted Solution

by:
DNK_Helpdesk earned 2000 total points
ID: 39662200
I had the same problem and after downgrading from XAMPP 1.8.3 to XAMPP 1.8.2 everything works as normal.
0
 

Author Closing Comment

by:rmartes
ID: 39666031
I reverted to xampp 1.8.2. This is not the only issue I had with xampp 1.8.3. Even though it is a test environment, I need it working at all times and don't have the time to spend hours troubleshooting.

Thank you so much.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

In this series, we will discuss common questions received as a database Solutions Engineer at Percona. In this role, we speak with a wide array of MySQL and MongoDB users responsible for both extremely large and complex environments to smaller singl…
In this blog post, we’ll look at how using thread_statistics can cause high memory usage.
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…

606 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question