Lost databaase unfortunately uninstalled xampp

Alles, was MariaDB und MySQL betrifft, kann hier besprochen werden.

Lost databaase unfortunately uninstalled xampp

Postby arsalan007 » 20. October 2017 15:49

Hi,

Hope you are doing well.

I am in a really big trouble and need quick response.
By mistake some one uninstalled xampp on my laptop and i had lost my all data including databases.
Please help how can i recover?
I tried with Active partition recovery (licensed Version) and it recovered my databases but how can i open that files are in .frm and .ibd format.
I just need to view the file if it can not be recovered in xampp just need the data.

Thanx
arsalan007
 
Posts: 2
Joined: 20. October 2017 15:46
XAMPP version: 3.*
Operating System: Windows 10

Re: Lost databaase unfortunately uninstalled xampp

Postby Altrea » 20. October 2017 17:09

Hi,

install exactly the same xampp version you have had before and copy the database files into your \mysql\data\ folder.

best wishes,
Altrea
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 8965
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: Lost databaase unfortunately uninstalled xampp

Postby arsalan007 » 21. October 2017 07:55

I did but getting this error on mysql log.

2017-10-21 12:14:46 12412 [Note] Plugin 'FEDERATED' is disabled.
2017-10-21 12:14:46 2300 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.
2017-10-21 12:14:46 12412 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-10-21 12:14:46 12412 [Note] InnoDB: The InnoDB memory heap is disabled
2017-10-21 12:14:46 12412 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-10-21 12:14:46 12412 [Note] InnoDB: Memory barrier is not used
2017-10-21 12:14:46 12412 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-10-21 12:14:46 12412 [Note] InnoDB: Not using CPU crc32 instructions
2017-10-21 12:14:46 12412 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-10-21 12:14:46 12412 [Note] InnoDB: Completed initialization of buffer pool
2017-10-21 12:14:47 12412 [Note] InnoDB: Highest supported file format is Barracuda.
2017-10-21 12:14:47 12412 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 40755583 in the ib_logfiles!
2017-10-21 12:14:47 12412 [Note] InnoDB: Database was not shutdown normally!
2017-10-21 12:14:47 12412 [Note] InnoDB: Starting crash recovery.
2017-10-21 12:14:47 12412 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-10-21 12:14:49 12412 [ERROR] InnoDB: Space id in fsp header 33001,but in the page header 84981784
2017-10-21 12:14:49 12412 [ERROR] InnoDB: checksum mismatch in tablespace .\db_pmmp\tb_companyprofile.ibd (table db_pmmp/tb_companyprofile)
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size:1024 Pages to analyze:64
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size:2048 Pages to analyze:48
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size:4096 Pages to analyze:24
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size:8192 Pages to analyze:12
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size:16384 Pages to analyze:6
2017-10-21 12:14:49 12412 [Note] InnoDB: Page size: 16384, Possible space_id count:0
InnoDB: Error: could not open single-table tablespace file .\db_pmmp\tb_companyprofile.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.
arsalan007
 
Posts: 2
Joined: 20. October 2017 15:46
XAMPP version: 3.*
Operating System: Windows 10

Re: Lost databaase unfortunately uninstalled xampp

Postby Nobbie » 21. October 2017 10:19

That looks as if the database file already has been overwritten and corrupted by new data. After deleting files and folders accidently you immediately should switch off the PC and get out the hard disk. There are too many sectors involved so i dont think that any recory tool can save your data after deleting them and writing new data to the disk. Dont you have any bakckup of your data?

Last not least, you might follow the 3. advice of the message above:

If the file system or the disk is broken, and you cannot remove the .ibd file, you can set innodb_force_recovery > 0 in my.cnf and force InnoDB to continue crash recovery here.


Thats the final idea i have, if this does not fix your data, sorry, it has gone.
Nobbie
 
Posts: 9771
Joined: 09. March 2008 13:04


Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 2 guests