MySQL Datenbank nach jeden stoppen zerschossen

In 10 Minuten startet der nächtliche Backupvorgang! Es kann währenddessen (ca. 10 Minuten) zu Einschränkungen bei der Nutzung des Forums kommen
Weitere Infos findet ihr im Thema Backup des Forums
  • Also es fing alles gestern an ich schaute mir die Viedeo von MrMonat an und erstellte eine Datenbank mit ID , Username ,pass , level . Nungut als ich dann heute morgen on kam startete mein MYSQL nicht . Ich hab gegooglet und mehrere sagten , dass meine ibdata1 in C:\xampp\mysql\data löschen sollte . Dies tat ich und mein MySQL startete wieder . Nach dem nächsten herunterfahren und anschlten passierte das gleiche . Ich installiete das Programm neu aber immer wieder das selbe . Wenn ich auf MySQL starte sehe ich nur :
    Attempting to start MySQL service... 22:16:24 [code=sql] Error: MySQL shutdown unexpectedly.
    22:16:24 [code=sql] This may be due to a blocked port, missing dependencies,
    22:16:24 [code=sql] improper privileges, a crash, or a shutdown by another method.
    22:16:24 [code=sql] Press the Logs button to view error logs and check
    22:16:24 [code=sql] the Windows Event Viewer for more clues
    22:16:24 [code=sql] If you need more help, copy and post this22:16:24 [code=sql] entire log window on the forums


    bis ich die ibdata1 lösche . Ich bitte um Hilfe . Mein skype name : derpr0 , danke !








    Dies ist mein Errorcode von der Errorlog :


    2013-10-30 21:59:38 5648 [Note] Plugin 'FEDERATED' is disabled.
    2013-10-30 21:59:38 338 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.
    2013-10-30 21:59:38 5648 [Note] InnoDB: The InnoDB memory heap is disabled
    2013-10-30 21:59:38 5648 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2013-10-30 21:59:38 5648 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2013-10-30 21:59:38 5648 [Note] InnoDB: Not using CPU crc32 instructions
    2013-10-30 21:59:38 5648 [Note] InnoDB: Initializing buffer pool, size = 16.0M
    2013-10-30 21:59:38 5648 [Note] InnoDB: Completed initialization of buffer pool
    2013-10-30 21:59:38 5648 [Note] InnoDB: Highest supported file format is Barracuda.
    2013-10-30 21:59:38 5648 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1614133 in the ib_logfiles!
    2013-10-30 21:59:38 5648 [Note] InnoDB: Database was not shutdown normally!
    2013-10-30 21:59:38 5648 [Note] InnoDB: Starting crash recovery.
    2013-10-30 21:59:38 5648 [Note] InnoDB: Reading tablespace information from the .ibd files...
    2013-10-30 21:59:38 5648 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace samp/user which uses space ID: 2 at filepath: .\samp\user.ibd
    InnoDB: Error: could not open single-table tablespace file .\samp\user.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.