was kann ich tun um mysql mit xampp 3.2.1 wieder starten zu können.
Ich hab die Datenbank copieren wollen. Das wurde aber wegen Timeout abgebrochen. Die DB war zudem noch in einem anderen Programm geöffnet.
Seitdem kommt dieser Fehler:
- Code: Select all
2015-06-07 10:22:05 3176 [Note] Plugin 'FEDERATED' is disabled.
2015-06-07 10:22:05 c6c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-07 10:22:05 3176 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-07 10:22:05 3176 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-07 10:22:05 3176 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-07 10:22:05 3176 [Note] InnoDB: Memory barrier is not used
2015-06-07 10:22:05 3176 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-07 10:22:05 3176 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-07 10:22:05 3176 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-07 10:22:05 3176 [Note] InnoDB: Completed initialization of buffer pool
2015-06-07 10:22:05 3176 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-07 10:22:05 3176 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 29927796 in the ib_logfiles!
2015-06-07 10:22:05 3176 [Note] InnoDB: Database was not shutdown normally!
2015-06-07 10:22:05 3176 [Note] InnoDB: Starting crash recovery.
2015-06-07 10:22:05 3176 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-07 10:22:05 3176 [Note] InnoDB: Restoring possible half-written data pages
2015-06-07 10:22:05 3176 [Note] InnoDB: from the doublewrite buffer...
2015-06-07 10:22:05 3176 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-07 10:22:05 3176 [Note] InnoDB: Waiting for purge to start
2015-06-07 10:22:05 3176 [Note] InnoDB: 5.6.21 started; log sequence number 29927796
2015-06-07 10:22:05 3176 [Note] Server hostname (bind-address): '*'; port: 3306
2015-06-07 10:22:05 3176 [Note] IPv6 is available.
2015-06-07 10:22:05 3176 [Note] - '::' resolves to '::';
2015-06-07 10:22:05 3176 [Note] Server socket created on IP: '::'.
2015-06-07 10:22:05 3176 [Note] Event Scheduler: Loaded 0 events
2015-06-07 10:22:05 3176 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.21' socket: '' port: 3306 MySQL Community Server (GPL)
2015-06-07 14:16:45 3176 [Note] Plugin 'FEDERATED' is disabled.
2015-06-07 14:16:45 c6c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-07 14:16:45 3176 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-07 14:16:45 3176 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-07 14:16:45 3176 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-07 14:16:45 3176 [Note] InnoDB: Memory barrier is not used
2015-06-07 14:16:45 3176 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-07 14:16:45 3176 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-07 14:16:45 3176 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-07 14:16:45 3176 [Note] InnoDB: Completed initialization of buffer pool
2015-06-07 14:16:45 3176 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-07 14:16:45 3176 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 34658401 in the ib_logfiles!
2015-06-07 14:16:45 3176 [Note] InnoDB: Database was not shutdown normally!
2015-06-07 14:16:45 3176 [Note] InnoDB: Starting crash recovery.
2015-06-07 14:16:45 3176 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-07 14:16:45 3176 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace vlps/albentb uses space ID: 111 at filepath: .\vlps\albentb.ibd. Cannot open tablespace vlps_save2/albentb which uses space ID: 111 at filepath: .\vlps_save2\albentb.ibd
InnoDB: Error: could not open single-table tablespace file .\vlps_save2\albentb.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
Gruß Rudi