# MySQL shutdown unexpectedly

2013-09-09 10:21:44 5776 [Note] Plugin 'FEDERATED' is disabled.
2013-09-09 10:21:44 1624 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-09-09 10:21:44 5776 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-09 10:21:44 5776 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-09 10:21:44 5776 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-09 10:21:44 5776 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-09 10:21:44 5776 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-09 10:21:44 5776 [Note] InnoDB: Completed initialization of buffer pool
2013-09-09 10:21:44 5776 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-09 10:21:44 5776 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 19862295 in the ib_logfiles!
2013-09-09 10:21:44 5776 [Note] InnoDB: Database was not shutdown normally!
2013-09-09 10:21:44 5776 [Note] InnoDB: Starting crash recovery.
2013-09-09 10:21:44 5776 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-09 10:21:44 5776 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace casualme/scraped_user uses space ID: 2 at filepath: .\casualme\scraped_user.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_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.


Hello guys.I need your help. my phpmyadmin is not working. How can i make it working again, i have a very large data, please help me how to fix this. i just want to get my database.

I have this following files. db.opt , scraped_user.frm , scraped_user.ibd is there a way to recover my database from this files?, I just want to get the tables data.

I want to reinstall my xampp but is there a way to back up my db when i can't run it? like copying this folder 'DBNAME' with files db.opt , scraped_user.frm , scraped_user.ibd

-
InnoDB was kind enough to include the steps/options you can take. Did you try any of them? –  lc. Sep 9 '13 at 2:40
i tried the first still not working in second i cant remove the .ibd file..i dont have a backup of my table. and i need that table.. on third i dont know where it is located. been looking for it.. –  Snippet Sep 9 '13 at 2:43

## migrated from stackoverflow.comSep 9 '13 at 4:21

This question came from our site for professional and enthusiast programmers.

I have manage to recover my data. (so happy) Im using XAMPP, i have a database DbScrapes with table scraped_user it is very important because it has 100k plus data that i've just gathered. When I restart my mysql. the crush occur. After hours of reading forums and solution i found a way to fix it,here's what i did in xampp i back up my old copy(after crush) of folder DbScrapes (dbname) from C:\xampp\mysql\data with files db.opt,scraped_user.frm,scraped_user.ibd also on C:\xampp\mysql\data i back up an old copy(after crush) of files ib_logfile0 , ib_logfile1 , ibdata1

Now.I Uninstalled my xampp, restart my computer to be sure ports that xampp is using will be close,check if there is a service of mysql in services.msc, on my computer there is a mysql service. so i delete it using cmd command sc delete "service_name", restart again to make sure everything is fresh. Then i install a new copy of xampp, after installation i test if apache and mysql is ok, if its ok click stop, then i copy the files that i have back up on the location where i get them so its C:\xampp\mysql\data, then run xampp's apache and mysql again. and now my im running xampp and i have my data

Note: Don't Delete ibdata1 it will delete all your database table.

Also the crushing issue. i think its a bug on xampp.

-
A bug? ibdata1 is the System Tablespace, so yes, if you delete that, you're blowing away your system. That's not a bug. dev.mysql.com/doc/refman/5.6/en/… –  Michael - sqlbot Sep 9 '13 at 16:42
nope. i don't mean the ibdata1, what i mean is that the crushing issue was a bug on xampp –  Snippet Sep 10 '13 at 3:15
Just add row innodb_force_recovery = 1 in my.ini file.