2014-03-14 10:03:18 1900 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: ready for connections.
Version: '5.6.10-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
2014-03-19 18:00:23 1900 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: Normal shutdown

2014-03-19 18:00:23 1900 [Note] Giving 2 client threads a chance to die gracefully
2014-03-19 18:00:23 1900 [Note] Event Scheduler: Purging the queue. 0 events
2014-03-19 18:00:23 1900 [Note] Shutting down slave threads
2014-03-19 18:00:25 1900 [Note] Forcefully disconnecting 2 remaining clients
2014-03-19 18:00:25 1900 [Warning] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: Forcing close of thread 546  user: 'katalog'

2014-03-19 18:00:25 1900 [Warning] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: Forcing close of thread 525  user: 'root'

2014-03-19 18:00:25 1900 [Note] Binlog end
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'partition'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_FT_INSERTED'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_METRICS'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_CMP'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'INNODB_TRX'
2014-03-19 18:00:26 1900 [Note] Shutting down plugin 'InnoDB'
2014-03-19 18:00:34 1900 [Note] InnoDB: FTS optimize thread exiting.
2014-03-19 18:00:34 1900 [Note] InnoDB: Starting shutdown...
2014-03-19 18:00:37 1900 [Note] InnoDB: Shutdown completed; log sequence number 2412797977
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'BLACKHOLE'
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'ARCHIVE'
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'MRG_MYISAM'
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'MyISAM'
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'MEMORY'
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'CSV'
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'sha256_password'
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'mysql_old_password'
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'mysql_native_password'
2014-03-19 18:00:37 1900 [Note] Shutting down plugin 'binlog'
2014-03-19 18:00:37 1900 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: Shutdown complete

2014-03-19 18:01:03 2204 [Note] Plugin 'FEDERATED' is disabled.
2014-03-19 18:01:03 2204 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-03-19 18:01:03 2204 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-19 18:01:03 2204 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-19 18:01:03 2204 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-19 18:01:03 2204 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-19 18:01:03 2204 [Note] InnoDB: Initializing buffer pool, size = 107.0M
2014-03-19 18:01:03 2204 [Note] InnoDB: Completed initialization of buffer pool
2014-03-19 18:01:03 2204 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_1' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_1'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_2' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_2'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_3' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_3'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_4' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_4'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_5' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_5'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_6' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_6'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_BEING_DELETED' to 'katalog/FTS_0000000000000efe_BEING_DELETED'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_BEING_DELETED_CACHE' to 'katalog/FTS_0000000000000efe_BEING_DELETED_CACHE'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_CONFIG' to 'katalog/FTS_0000000000000efe_CONFIG'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_DELETED' to 'katalog/FTS_0000000000000efe_DELETED'.
2014-03-19 18:01:16 2204 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_DELETED_CACHE' to 'katalog/FTS_0000000000000efe_DELETED_CACHE'.
2014-03-19 18:01:16 10f8  InnoDB: Assertion failure in thread 4344 in file fts0fts.cc line 6087
InnoDB: Failing assertion: fts_table.suffix != NULL
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.
2014-03-19 18:01:44 2280 [Note] Plugin 'FEDERATED' is disabled.
2014-03-19 18:01:44 2280 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-03-19 18:01:44 2280 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-19 18:01:44 2280 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-19 18:01:44 2280 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-19 18:01:44 2280 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-19 18:01:44 2280 [Note] InnoDB: Initializing buffer pool, size = 107.0M
2014-03-19 18:01:44 2280 [Note] InnoDB: Completed initialization of buffer pool
2014-03-19 18:01:44 2280 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-19 18:01:45 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_BEING_DELETED'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Tablespace open failed for '"katalog"."FTS_0000000000003838_BEING_DELETED"', ignored.
2014-03-19 18:01:45 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_BEING_DELETED_CACHE'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Tablespace open failed for '"katalog"."FTS_0000000000003838_BEING_DELETED_CACHE"', ignored.
2014-03-19 18:01:45 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_CONFIG'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Tablespace open failed for '"katalog"."FTS_0000000000003838_CONFIG"', ignored.
2014-03-19 18:01:45 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_DELETED'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Tablespace open failed for '"katalog"."FTS_0000000000003838_DELETED"', ignored.
2014-03-19 18:01:45 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_DELETED_CACHE'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:45 2280 [ERROR] InnoDB: Tablespace open failed for '"katalog"."FTS_0000000000003838_DELETED_CACHE"', ignored.
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_BEING_DELETED"' in the cache. Attempting to load the tablespace with space id 1057.
2014-03-19 18:01:46 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_BEING_DELETED'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_BEING_DELETED_CACHE"' in the cache. Attempting to load the tablespace with space id 1058.
2014-03-19 18:01:46 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_BEING_DELETED_CACHE'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_CONFIG"' in the cache. Attempting to load the tablespace with space id 1059.
2014-03-19 18:01:46 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_CONFIG'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_DELETED"' in the cache. Attempting to load the tablespace with space id 1055.
2014-03-19 18:01:46 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_DELETED'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_DELETED_CACHE"' in the cache. Attempting to load the tablespace with space id 1056.
2014-03-19 18:01:46 f0c  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.6/en/operating-system-error-codes.html
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_DELETED_CACHE'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_1' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_1'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_2' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_2'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_3' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_3'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_4' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_4'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_5' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_5'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_6' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_6'.
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Table katalog/FTS_0000000000003838_BEING_DELETED does not have an .ibd file in the database directory. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2014-03-19 18:01:46 2280 [Warning] InnoDB: Failed to rename aux table 'katalog/FTS_0000000000003838_BEING_DELETED' to new format 'katalog/FTS_0000000000000efe_BEING_DELETED'. 
2014-03-19 18:01:46 2280 [Warning] InnoDB: Failed to rename one aux table katalog/FTS_0000000000003838_BEING_DELETED Will revert all successful rename operations.
2014-03-19 18:01:46 2280 [ERROR] InnoDB: Table katalog/FTS_0000000000003838_BEING_DELETED does not have an .ibd file in the database directory. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2014-03-19 18:01:46 2280 [Warning] InnoDB: Failed to revert table katalog/FTS_0000000000003838_BEING_DELETED. Please revert manually.
2014-03-19 18:01:46 2280 [Warning] InnoDB: Rollback operations on all aux tables of table katalog/auf. Please check why renaming aux tables failed, and restart the server to upgrade again to get the table work.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003853_0000000000005112_INDEX_6' to 'katalog/FTS_0000000000000f0d_00000000000013f8_INDEX_6'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003853_BEING_DELETED_CACHE' to 'katalog/FTS_0000000000000f0d_BEING_DELETED_CACHE'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003853_CONFIG' to 'katalog/FTS_0000000000000f0d_CONFIG'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003853_DELETED' to 'katalog/FTS_0000000000000f0d_DELETED'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003853_DELETED_CACHE' to 'katalog/FTS_0000000000000f0d_DELETED_CACHE'.
2014-03-19 18:01:46 2280 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003853_0000000000005112_INDEX_5' to 'katalog/FTS_0000000000000f0d_00000000000013f8_INDEX_5'.
2014-03-19 18:01:46 f0c  InnoDB: Assertion failure in thread 3852 in file fts0fts.cc line 6087
InnoDB: Failing assertion: fts_table.suffix != NULL
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.
2014-03-19 18:16:12 3772 [Note] Plugin 'FEDERATED' is disabled.
2014-03-19 18:16:12 3772 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-03-19 18:16:12 3772 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-19 18:16:12 3772 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-19 18:16:13 3772 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-19 18:16:13 3772 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-19 18:16:13 3772 [Note] InnoDB: Initializing buffer pool, size = 107.0M
2014-03-19 18:16:13 3772 [Note] InnoDB: Completed initialization of buffer pool
2014-03-19 18:16:13 3772 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-19 18:16:13 3772 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2412797977
2014-03-19 18:16:13 3772 [Note] InnoDB: Database was not shutdown normally!
2014-03-19 18:16:13 3772 [Note] InnoDB: Starting crash recovery.
2014-03-19 18:16:13 3772 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-19 18:16:13 3772 [Note] InnoDB: Restoring possible half-written data pages 
2014-03-19 18:16:13 3772 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2412801907
2014-03-19 18:16:15 3772 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2014-03-19 18:16:15 7d0  InnoDB: Error: table 'katalog/FTS_0000000000003838_BEING_DELETED'
InnoDB: in InnoDB data dictionary has tablespace id 1057,
InnoDB: but the tablespace with that id has name katalog/FTS_0000000000000efe_BEING_DELETED.
InnoDB: Have 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.
2014-03-19 18:16:15 7d0  InnoDB: Error: table 'katalog/FTS_0000000000003838_BEING_DELETED_CACHE'
InnoDB: in InnoDB data dictionary has tablespace id 1058,
InnoDB: but the tablespace with that id has name katalog/FTS_0000000000000efe_BEING_DELETED_CACHE.
InnoDB: Have 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.
2014-03-19 18:16:15 7d0  InnoDB: Error: table 'katalog/FTS_0000000000003838_CONFIG'
InnoDB: in InnoDB data dictionary has tablespace id 1059,
InnoDB: but the tablespace with that id has name katalog/FTS_0000000000000efe_CONFIG.
InnoDB: Have 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.
2014-03-19 18:16:15 7d0  InnoDB: Error: table 'katalog/FTS_0000000000003838_DELETED'
InnoDB: in InnoDB data dictionary has tablespace id 1055,
InnoDB: but the tablespace with that id has name katalog/FTS_0000000000000efe_DELETED.
InnoDB: Have 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.
2014-03-19 18:16:15 7d0  InnoDB: Error: table 'katalog/FTS_0000000000003838_DELETED_CACHE'
InnoDB: in InnoDB data dictionary has tablespace id 1056,
InnoDB: but the tablespace with that id has name katalog/FTS_0000000000000efe_DELETED_CACHE.
InnoDB: Have 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.
2014-03-19 18:16:15 7d0  InnoDB: Error: table 'katalog/FTS_0000000000003853_BEING_DELETED_CACHE'
InnoDB: in InnoDB data dictionary has tablespace id 1067,
InnoDB: but the tablespace with that id has name katalog/FTS_0000000000000f0d_BEING_DELETED_CACHE.
InnoDB: Have 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.
2014-03-19 18:16:16 7d0  InnoDB: Error: table 'katalog/FTS_0000000000003853_CONFIG'
InnoDB: in InnoDB data dictionary has tablespace id 1068,
InnoDB: but the tablespace with that id has name katalog/FTS_0000000000000f0d_CONFIG.
InnoDB: Have 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.
2014-03-19 18:16:16 7d0  InnoDB: Error: table 'katalog/FTS_0000000000003853_DELETED'
InnoDB: in InnoDB data dictionary has tablespace id 1064,
InnoDB: but the tablespace with that id has name katalog/FTS_0000000000000f0d_DELETED.
InnoDB: Have 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.
2014-03-19 18:16:16 7d0  InnoDB: Error: table 'katalog/FTS_0000000000003853_DELETED_CACHE'
InnoDB: in InnoDB data dictionary has tablespace id 1065,
InnoDB: but the tablespace with that id has name katalog/FTS_0000000000000f0d_DELETED_CACHE.
InnoDB: Have 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.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_BEING_DELETED"' in the cache. Attempting to load the tablespace with space id 1057.
2014-03-19 18:16:16 7d0  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.6/en/operating-system-error-codes.html
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_BEING_DELETED'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_BEING_DELETED_CACHE"' in the cache. Attempting to load the tablespace with space id 1058.
2014-03-19 18:16:16 7d0  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.6/en/operating-system-error-codes.html
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_BEING_DELETED_CACHE'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_CONFIG"' in the cache. Attempting to load the tablespace with space id 1059.
2014-03-19 18:16:16 7d0  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.6/en/operating-system-error-codes.html
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_CONFIG'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_DELETED"' in the cache. Attempting to load the tablespace with space id 1055.
2014-03-19 18:16:16 7d0  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.6/en/operating-system-error-codes.html
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_DELETED'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003838_DELETED_CACHE"' in the cache. Attempting to load the tablespace with space id 1056.
2014-03-19 18:16:16 7d0  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.6/en/operating-system-error-codes.html
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003838_DELETED_CACHE'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_1' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_1'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_2' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_2'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_3' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_3'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_4' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_4'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_5' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_5'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003838_0000000000005084_INDEX_6' to 'katalog/FTS_0000000000000efe_00000000000013dc_INDEX_6'.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Table katalog/FTS_0000000000003838_BEING_DELETED does not have an .ibd file in the database directory. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2014-03-19 18:16:16 3772 [Warning] InnoDB: Failed to rename aux table 'katalog/FTS_0000000000003838_BEING_DELETED' to new format 'katalog/FTS_0000000000000efe_BEING_DELETED'. 
2014-03-19 18:16:16 3772 [Warning] InnoDB: Failed to rename one aux table katalog/FTS_0000000000003838_BEING_DELETED Will revert all successful rename operations.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Table katalog/FTS_0000000000003838_BEING_DELETED does not have an .ibd file in the database directory. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2014-03-19 18:16:16 3772 [Warning] InnoDB: Failed to revert table katalog/FTS_0000000000003838_BEING_DELETED. Please revert manually.
2014-03-19 18:16:16 3772 [Warning] InnoDB: Rollback operations on all aux tables of table katalog/auf. Please check why renaming aux tables failed, and restart the server to upgrade again to get the table work.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003853_BEING_DELETED_CACHE"' in the cache. Attempting to load the tablespace with space id 1067.
2014-03-19 18:16:16 7d0  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.6/en/operating-system-error-codes.html
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003853_BEING_DELETED_CACHE'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003853_CONFIG"' in the cache. Attempting to load the tablespace with space id 1068.
2014-03-19 18:16:16 7d0  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.6/en/operating-system-error-codes.html
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003853_CONFIG'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003853_DELETED"' in the cache. Attempting to load the tablespace with space id 1064.
2014-03-19 18:16:16 7d0  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.6/en/operating-system-error-codes.html
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003853_DELETED'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Failed to find tablespace for table '"katalog"."FTS_0000000000003853_DELETED_CACHE"' in the cache. Attempting to load the tablespace with space id 1065.
2014-03-19 18:16:16 7d0  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.6/en/operating-system-error-codes.html
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Could not find a valid tablespace file for 'katalog/FTS_0000000000003853_DELETED_CACHE'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003853_0000000000005112_INDEX_6' to 'katalog/FTS_0000000000000f0d_00000000000013f8_INDEX_6'.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Table katalog/FTS_0000000000003853_BEING_DELETED_CACHE does not have an .ibd file in the database directory. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2014-03-19 18:16:16 3772 [Warning] InnoDB: Failed to rename aux table 'katalog/FTS_0000000000003853_BEING_DELETED_CACHE' to new format 'katalog/FTS_0000000000000f0d_BEING_DELETED_CACHE'. 
2014-03-19 18:16:16 3772 [Warning] InnoDB: Failed to rename one aux table katalog/FTS_0000000000003853_BEING_DELETED_CACHE Will revert all successful rename operations.
2014-03-19 18:16:16 3772 [ERROR] InnoDB: Table katalog/FTS_0000000000003853_BEING_DELETED_CACHE does not have an .ibd file in the database directory. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2014-03-19 18:16:16 3772 [Warning] InnoDB: Failed to revert table katalog/FTS_0000000000003853_BEING_DELETED_CACHE. Please revert manually.
2014-03-19 18:16:16 3772 [Warning] InnoDB: Rollback operations on all aux tables of table katalog/bib. Please check why renaming aux tables failed, and restart the server to upgrade again to get the table work.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_CONFIG' to 'katalog/FTS_0000000000000f1c_CONFIG'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_BEING_DELETED_CACHE' to 'katalog/FTS_0000000000000f1c_BEING_DELETED_CACHE'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_BEING_DELETED' to 'katalog/FTS_0000000000000f1c_BEING_DELETED'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_0000000000005131_INDEX_6' to 'katalog/FTS_0000000000000f1c_000000000000140b_INDEX_6'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_0000000000005131_INDEX_5' to 'katalog/FTS_0000000000000f1c_000000000000140b_INDEX_5'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_0000000000005131_INDEX_4' to 'katalog/FTS_0000000000000f1c_000000000000140b_INDEX_4'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_0000000000005131_INDEX_3' to 'katalog/FTS_0000000000000f1c_000000000000140b_INDEX_3'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_0000000000005131_INDEX_2' to 'katalog/FTS_0000000000000f1c_000000000000140b_INDEX_2'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_0000000000005131_INDEX_1' to 'katalog/FTS_0000000000000f1c_000000000000140b_INDEX_1'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_DELETED_CACHE' to 'katalog/FTS_0000000000000f1c_DELETED_CACHE'.
2014-03-19 18:16:16 3772 [Note] InnoDB: Renamed aux table 'katalog/FTS_0000000000003868_DELETED' to 'katalog/FTS_0000000000000f1c_DELETED'.
2014-03-19 18:16:16 7d0  InnoDB: Assertion failure in thread 2000 in file fts0fts.cc line 6087
InnoDB: Failing assertion: fts_table.suffix != NULL
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.