1

After a server issue, my client has restored the MySQL files before their issue, but MySQL is having problems bringing their database back up. (i'm waiting for more information as the exact nature of the issue)

I have the ibdata1 ib_logfile0, and ib_logfile1files, and all the .frm and .ibd files for all the tables. I can open the database using Navicat, but when trying to open individual tables the first attempt shuts down the MySQL service and after restarting it, table access attempts returns a message that the table doesn't exist.

I've uploaded the section of the error log from my last attempt to access the database.

I've contacted percona and am aware of their tools, and services, but was hoping someone could give me a little more insight to my issue, and if there is a way to restore this database that isn't a major time consuming pain in the butt. :)

Thanks,

Server issue specifics:

The server crash was the result of a power surge, which took out the SATA and RAID controllers. It also completely damaged one drive (there were 2 drives mirrored in RAID1 as dynamic disks). The other drive was only partially damaged, and it is from this drive that we extracted the files that we have from the mysql data directory (that is the "afriplexqms" directory you're seeing).

However, we also have a manual backup set, which is in the root of the D:\IRENE\TLM folder (in the form of 342 .sql files).

Edited by archibald_1

Attachments
2015-05-07 00:48:59 5344 [Note] Plugin 'FEDERATED' is disabled.
2015-05-07 00:48:59 1454 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.
2015-05-07 00:48:59 5344 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-07 00:48:59 5344 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-07 00:48:59 5344 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-07 00:48:59 5344 [Note] InnoDB: Memory barrier is not used
2015-05-07 00:48:59 5344 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-07 00:48:59 5344 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-07 00:48:59 5344 [Note] InnoDB: Initializing buffer pool, size = 6.0G
2015-05-07 00:49:00 5344 [Note] InnoDB: Completed initialization of buffer pool
2015-05-07 00:49:00 5344 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-07 00:49:00 5344 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*3456 pages, LSN=20911902
2015-05-07 00:49:00 5344 [Warning] InnoDB: Starting to delete and rewrite log files.
2015-05-07 00:49:00 5344 [Note] InnoDB: Setting log file .\ib_logfile101 size to 54 MB
2015-05-07 00:49:01 5344 [Note] InnoDB: Setting log file .\ib_logfile1 size to 54 MB
2015-05-07 00:49:01 5344 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
2015-05-07 00:49:01 5344 [Warning] InnoDB: New log files created, LSN=20911902
2015-05-07 00:49:01 5344 [Note] InnoDB: 128 rollback segment(s) are active.
2015-05-07 00:49:01 5344 [Note] InnoDB: Waiting for purge to start
2015-05-07 00:49:01 5344 [Note] InnoDB: 5.6.23 started; log sequence number 20911902
2015-05-07 00:49:01 5344 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
2015-05-07 00:49:01 5344 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
2015-05-07 00:49:01 5344 [Note] Server socket created on IP: '0.0.0.0'.
2015-05-07 00:49:01 5344 [Note] Event Scheduler: Loaded 0 events
2015-05-07 00:49:01 5344 [Note] Event Scheduler: scheduler thread started with id 1
2015-05-07 00:49:01 5344 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: ready for connections.
Version: '5.6.23-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
InnoDB: Error: tablespace id is 9 in the data dictionary
InnoDB: but in file .\afriplexqms\contacts.ibd it is 747!
2015-05-07 00:49:27 4d0  InnoDB: Assertion failure in thread 1232 in file fil0fil.cc line 796
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2015-05-07 00:50:08 3920 [Note] Plugin 'FEDERATED' is disabled.
2015-05-07 00:50:08 142c 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.
2015-05-07 00:50:08 3920 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-07 00:50:08 3920 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-07 00:50:08 3920 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-07 00:50:08 3920 [Note] InnoDB: Memory barrier is not used
2015-05-07 00:50:08 3920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-07 00:50:08 3920 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-07 00:50:08 3920 [Note] InnoDB: Initializing buffer pool, size = 6.0G
2015-05-07 00:50:09 3920 [Note] InnoDB: Completed initialization of buffer pool
2015-05-07 00:50:09 3920 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-07 00:50:09 3920 [Note] InnoDB: The log sequence numbers 20911902 and 20911902 in ibdata files do not match the log sequence number 20912150 in the ib_logfiles!
2015-05-07 00:50:09 3920 [Note] InnoDB: Database was not shutdown normally!
2015-05-07 00:50:09 3920 [Note] InnoDB: Starting crash recovery.
2015-05-07 00:50:09 3920 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-07 00:50:09 3920 [Note] InnoDB: Restoring possible half-written data pages 
2015-05-07 00:50:09 3920 [Note] InnoDB: from the doublewrite buffer...
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/checktlm'
InnoDB: in InnoDB data dictionary has tablespace id 6,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/checktlm and id 1085, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/companyactionplantext'
InnoDB: in InnoDB data dictionary has tablespace id 7,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/companyactionplantext and id 745, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/companyinfo'
InnoDB: in InnoDB data dictionary has tablespace id 8,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/companyinfo and id 746, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/contacts'
InnoDB: in InnoDB data dictionary has tablespace id 9,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/contacts and id 747, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/flowchartcombo1procedure'
InnoDB: in InnoDB data dictionary has tablespace id 10,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/flowchartcombo1procedure and id 748, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/flowchartcombo2kpi'
InnoDB: in InnoDB data dictionary has tablespace id 11,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/flowchartcombo2kpi and id 749, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/followupplans'
InnoDB: in InnoDB data dictionary has tablespace id 12,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/followupplans and id 750, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/qb_primarytables'
InnoDB: in InnoDB data dictionary has tablespace id 13,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/qb_primarytables and id 752, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/qbaccounts'
InnoDB: in InnoDB data dictionary has tablespace id 14,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/qbaccounts and id 751, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/receivepaymenttlm'
InnoDB: in InnoDB data dictionary has tablespace id 15,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/receivepaymenttlm and id 753, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/reftbldoctypes'
InnoDB: in InnoDB data dictionary has tablespace id 16,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/reftbldoctypes and id 754, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:50:09 142c  InnoDB: Error: table 'afriplexqms/salestaxtlm'
InnoDB: in InnoDB data dictionary has tablespace id 17,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name afriplexqms/salestaxtlm and id 755, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2015-05-07 00:
2
Contributors
3
Replies
16
Views
1 Year
Discussion Span
Last Post by rproffitt
0

I have to ask why the date on the logs are last year.

-> Why is the date on the logs from last year?

Many systems blow up if the date+time is too far off.

0

Time to make new logs of what's up. Be sure to remove lines that are common to such logs to not be distracted by DEPRACTED items.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.