>>


150130 19:48:20 [Note] Plugin 'FEDERATED' is disabled.
150130 19:48:21  InnoDB: Started; log sequence number 15 3705883514
150130 19:48:21 [Note] Event Scheduler: Loaded 0 events
150130 19:48:21 [Note] E:\Program Files (x86)\McAfee\MySQL for Quarantine Manager\bin\mysqld.exe: ready for connections.
Version: '5.1.42-community'  socket: ''  port: 3306  MySQL Community Server (GPL)
150422  4:47:57  InnoDB: ERROR: the age of the last checkpoint is 60397828,
InnoDB: which exceeds the log group capacity 60394292.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
150503  0:14:29  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: File name E:\Program Files (x86)\McAfee\MySQL for Quarantine Manager\Temp\#sql5a4_1009e1_28.ibd
InnoDB: File operation call: 'open'.
150503  0:14:29  InnoDB: Assertion failure in thread 15736 in file .\fil\fil0fil.c line 635
InnoDB: Failing assertion: ret
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 2240 stopped in file G:\mysql-5.1.42-winbuild\mysql-community-nt-5.1.42-build\storage\innobase\include\sync0sync.ic line 115
150503  0:14:29 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=67108864
read_buffer_size=524288
max_used_connections=459
max_threads=500
threads_connected=37
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2373996 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2e95a9f0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
000000014025679D    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
0000000140259AB3    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
000000014025C84B    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
00000001402A4A81    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
00000001402A4E22    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
0000000140261F20    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
000000014028D65F    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
000000014028E630    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
000000014028BAE5    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
0000000140285A6B    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
0000000140285D36    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
0000000140285EE7    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
000000014025F53D    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
000000014025FC30    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
000000014025FDBF    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
0000000140260013    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
000000014021E871    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
0000000140210D76    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
0000000140074507    mysqld.exe!?rm_temporary_table@@YA_NPEAUhandlerton@@PEAD@Z()
000000014007623B    mysqld.exe!?close_temporary@@YAXPEAUst_table@@_N1@Z()
0000000140077F70    mysqld.exe!?close_temporary_tables@@YAXPEAVTHD@@@Z()
0000000140058854    mysqld.exe!?cleanup@THD@@QEAAXXZ()
000000014001708E    mysqld.exe!?unlink_thd@@YAXPEAVTHD@@@Z()
000000014001A63E    mysqld.exe!?one_thread_per_connection_end@@YA_NPEAVTHD@@_N@Z()
00000001400974F9    mysqld.exe!handle_one_connection()
0000000140318EA5    mysqld.exe!pthread_start()
00000001402E2FD7    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
00000001402E30A5    mysqld.exe!?check_next_symbol@Gis_read_stream@@QEAA_ND@Z()
000007F8D0401842    KERNEL32.DLL!BaseThreadInitThunk()
000007F8D2BFF9D1    ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0000000000000000=(null)
thd->thread_id=1051105
thd->killed=KILL_CONNECTION
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
InnoDB: Thread 9832 stopped in file .\handler\ha_innodb.cc line 6078
InnoDB: Thread 2236 stopped in file G:\mysql-5.1.42-winbuild\mysql-community-nt-5.1.42-build\storage\innobase\include\sync0sync.ic line 115
150506 13:33:52 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Log scan progressed past the checkpoint lsn 29 2117773324
150506 13:33:52  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 29 2123016192
InnoDB: Doing recovery: scanned up to log sequence number 29 2127520836
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_0'
InnoDB: in InnoDB data dictionary has tablespace id 12161069,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_1'
InnoDB: in InnoDB data dictionary has tablespace id 12161070,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_10'
InnoDB: in InnoDB data dictionary has tablespace id 12161080,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_12'
InnoDB: in InnoDB data dictionary has tablespace id 12161081,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_13'
InnoDB: in InnoDB data dictionary has tablespace id 12161082,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_15'
InnoDB: in InnoDB data dictionary has tablespace id 12161083,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_16'
InnoDB: in InnoDB data dictionary has tablespace id 12161084,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_18'
InnoDB: in InnoDB data dictionary has tablespace id 12161085,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_19'
InnoDB: in InnoDB data dictionary has tablespace id 12161086,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_1b'
InnoDB: in InnoDB data dictionary has tablespace id 12161087,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_1c'
InnoDB: in InnoDB data dictionary has tablespace id 12161088,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_1e'
InnoDB: in InnoDB data dictionary has tablespace id 12161089,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_1f'
InnoDB: in InnoDB data dictionary has tablespace id 12161090,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_21'
InnoDB: in InnoDB data dictionary has tablespace id 12161091,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_22'
InnoDB: in InnoDB data dictionary has tablespace id 12161092,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_24'
InnoDB: in InnoDB data dictionary has tablespace id 12161093,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_25'
InnoDB: in InnoDB data dictionary has tablespace id 12161094,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_27'
InnoDB: in InnoDB data dictionary has tablespace id 12161095,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_28'
InnoDB: in InnoDB data dictionary has tablespace id 12161096,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_3'
InnoDB: in InnoDB data dictionary has tablespace id 12161071,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_4'
InnoDB: in InnoDB data dictionary has tablespace id 12161072,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_6'
InnoDB: in InnoDB data dictionary has tablespace id 12161073,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_7'
InnoDB: in InnoDB data dictionary has tablespace id 12161074,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_9'
InnoDB: in InnoDB data dictionary has tablespace id 12161075,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_a'
InnoDB: in InnoDB data dictionary has tablespace id 12161076,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_c'
InnoDB: in InnoDB data dictionary has tablespace id 12161077,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_d'
InnoDB: in InnoDB data dictionary has tablespace id 12161078,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Error: table 'temp/#sql5a4_1009e1_f'
InnoDB: in InnoDB data dictionary has tablespace id 12161079,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:56  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
150506 13:33:58  InnoDB: Started; log sequence number 29 2127520836
150506 13:33:58  InnoDB: error: space object of table temp/#sql5a4_1009e1_0,
InnoDB: space id 12161069 did not exist in memory. Retrying an open.
150506 13:33:58  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:58  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:58  InnoDB: Error: table 'temp/#sql5a4_1009e1_0'
InnoDB: in InnoDB data dictionary has tablespace id 12161069,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:58 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_0'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_0'>.
150506 13:33:58  InnoDB: error: space object of table temp/#sql5a4_1009e1_1,
InnoDB: space id 12161070 did not exist in memory. Retrying an open.
150506 13:33:58  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:58  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_1.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:58  InnoDB: Error: table 'temp/#sql5a4_1009e1_1'
InnoDB: in InnoDB data dictionary has tablespace id 12161070,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:58 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_1'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_1'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_10,
InnoDB: space id 12161080 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_10.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_10'
InnoDB: in InnoDB data dictionary has tablespace id 12161080,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_10'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_10'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_12,
InnoDB: space id 12161081 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_12.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_12'
InnoDB: in InnoDB data dictionary has tablespace id 12161081,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_12'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_12'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_13,
InnoDB: space id 12161082 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_13.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_13'
InnoDB: in InnoDB data dictionary has tablespace id 12161082,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_13'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_13'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_15,
InnoDB: space id 12161083 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_15.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_15'
InnoDB: in InnoDB data dictionary has tablespace id 12161083,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_15'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_15'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_16,
InnoDB: space id 12161084 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_16.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_16'
InnoDB: in InnoDB data dictionary has tablespace id 12161084,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_16'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_16'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_18,
InnoDB: space id 12161085 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_18.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_18'
InnoDB: in InnoDB data dictionary has tablespace id 12161085,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_18'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_18'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_19,
InnoDB: space id 12161086 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_19.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_19'
InnoDB: in InnoDB data dictionary has tablespace id 12161086,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_19'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_19'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_1b,
InnoDB: space id 12161087 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_1b.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_1b'
InnoDB: in InnoDB data dictionary has tablespace id 12161087,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_1b'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_1b'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_1c,
InnoDB: space id 12161088 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_1c.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_1c'
InnoDB: in InnoDB data dictionary has tablespace id 12161088,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_1c'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_1c'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_1e,
InnoDB: space id 12161089 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_1e.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_1e'
InnoDB: in InnoDB data dictionary has tablespace id 12161089,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_1e'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_1e'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_1f,
InnoDB: space id 12161090 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_1f.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_1f'
InnoDB: in InnoDB data dictionary has tablespace id 12161090,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_1f'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_1f'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_21,
InnoDB: space id 12161091 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_21.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_21'
InnoDB: in InnoDB data dictionary has tablespace id 12161091,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_21'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_21'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_22,
InnoDB: space id 12161092 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_22.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_22'
InnoDB: in InnoDB data dictionary has tablespace id 12161092,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_22'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_22'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_24,
InnoDB: space id 12161093 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_24.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_24'
InnoDB: in InnoDB data dictionary has tablespace id 12161093,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_24'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_24'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_25,
InnoDB: space id 12161094 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_25.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_25'
InnoDB: in InnoDB data dictionary has tablespace id 12161094,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_25'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_25'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_27,
InnoDB: space id 12161095 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_27.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_27'
InnoDB: in InnoDB data dictionary has tablespace id 12161095,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_27'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_27'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_3,
InnoDB: space id 12161071 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_3.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_3'
InnoDB: in InnoDB data dictionary has tablespace id 12161071,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_3'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_3'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_4,
InnoDB: space id 12161072 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_4.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_4'
InnoDB: in InnoDB data dictionary has tablespace id 12161072,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_4'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_4'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_6,
InnoDB: space id 12161073 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_6.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_6'
InnoDB: in InnoDB data dictionary has tablespace id 12161073,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_6'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_6'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_7,
InnoDB: space id 12161074 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_7.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_7'
InnoDB: in InnoDB data dictionary has tablespace id 12161074,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_7'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_7'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_9,
InnoDB: space id 12161075 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_9.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_9'
InnoDB: in InnoDB data dictionary has tablespace id 12161075,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_9'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_9'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_a,
InnoDB: space id 12161076 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_a.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_a'
InnoDB: in InnoDB data dictionary has tablespace id 12161076,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_a'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_a'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_c,
InnoDB: space id 12161077 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_c.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_c'
InnoDB: in InnoDB data dictionary has tablespace id 12161077,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_c'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_c'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_d,
InnoDB: space id 12161078 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_d.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_d'
InnoDB: in InnoDB data dictionary has tablespace id 12161078,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_d'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_d'>.
150506 13:33:59  InnoDB: error: space object of table temp/#sql5a4_1009e1_f,
InnoDB: space id 12161079 did not exist in memory. Retrying an open.
150506 13:33:59  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
150506 13:33:59  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\temp\#sql5a4_1009e1_f.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
150506 13:33:59  InnoDB: Error: table 'temp/#sql5a4_1009e1_f'
InnoDB: in InnoDB data dictionary has tablespace id 12161079,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table 150506 13:33:59 [Warning] Invalid (old?) table or database name '#sql5a4_1009e1_f'
`temp`.<result 2 when explaining filename '#sql5a4_1009e1_f'>.
150506 13:33:59 [Note] Event Scheduler: Loaded 0 events
150506 13:33:59 [Note] E:\Program Files (x86)\McAfee\MySQL for Quarantine Manager\bin\mysqld.exe: ready for connections.
Version: '5.1.42-community'  socket: ''  port: 3306  MySQL Community Server (GPL)

>>>