Tijden veranderen
Xampp, mysql
Code (php)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
2013-10-10 18:38:46 3848 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 18:38:46 ba0 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-10 18:38:46 3848 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 18:38:46 3848 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 18:38:46 3848 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 18:38:46 3848 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 18:38:46 3848 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 18:38:46 3848 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 18:38:46 3848 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 18:38:46 3848 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600614 in the ib_logfiles!
2013-10-10 18:38:46 3848 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 18:38:46 3848 [Note] InnoDB: Starting crash recovery.
2013-10-10 18:38:46 3848 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 18:38:46 3848 [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 webshop/boardgame which uses space ID: 2 at filepath: .\webshop\boardgame.ibd
InnoDB: Error: could not open single-table tablespace file .\webshop\boardgame.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.
2013-10-10 18:38:46 ba0 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-10 18:38:46 3848 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 18:38:46 3848 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 18:38:46 3848 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 18:38:46 3848 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 18:38:46 3848 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 18:38:46 3848 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 18:38:46 3848 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 18:38:46 3848 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600614 in the ib_logfiles!
2013-10-10 18:38:46 3848 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 18:38:46 3848 [Note] InnoDB: Starting crash recovery.
2013-10-10 18:38:46 3848 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 18:38:46 3848 [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 webshop/boardgame which uses space ID: 2 at filepath: .\webshop\boardgame.ibd
InnoDB: Error: could not open single-table tablespace file .\webshop\boardgame.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.
Dit kon ik oplossen door de 'ibdata1' file onder xampp/mysql/data te verwijderen, helaas heeft dit als gevolg dat ik mijn gehele database telkens verlies, hoe kan ik er voor zorgen dat ik deze behoud.
Ik had een backup gemaakt en probeerde deze te importeren, maar hij gaf deze error:
Code (php)
1
2
3
4
5
6
7
8
2
3
4
5
6
7
8
Fout
SQL-query:
-- -- Databank: `webshop` -- -- -------------------------------------------------------- -- -- Tabelstructuur voor tabel `bg` -- CREATE TABLE IF NOT EXISTS `bg` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(100) COLLATE utf8_bin NOT NULL, `price` int(11) NOT NULL, `promo` int(11) NOT NULL, `description` text COLLATE utf8_bin NOT NULL, `minplayer` int(11) NOT NULL, `maxplayer` int(11) NOT NULL, `playtime` int(11) NOT NULL, `age` int(11) NOT NULL, `category` varchar(100) COLLATE utf8_bin NOT NULL, `author` varchar(100) COLLATE utf8_bin NOT NULL, `artist` varchar(100) COLLATE utf8_bin NOT NULL, `publisher` varchar(100) COLLATE utf8_bin NOT NULL, `publishdate` int(11) NOT NULL, `img1` varchar(500) COLLATE utf8_bin NOT NULL, `img2` varchar(500) COLLATE utf8_bin NOT NULL, `img3` varchar(500) COLLATE utf8_bin NOT NULL, `language` varchar(100) COLLATE utf8_bin NOT NULL, `gewicht` int(11) NOT NULL, `afmetingen` varchar(100) COLLATE utf8_bin [...]
MySQL meldt: Documentatie
#1146 - Table 'webshop.bg' doesn't exist
SQL-query:
-- -- Databank: `webshop` -- -- -------------------------------------------------------- -- -- Tabelstructuur voor tabel `bg` -- CREATE TABLE IF NOT EXISTS `bg` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(100) COLLATE utf8_bin NOT NULL, `price` int(11) NOT NULL, `promo` int(11) NOT NULL, `description` text COLLATE utf8_bin NOT NULL, `minplayer` int(11) NOT NULL, `maxplayer` int(11) NOT NULL, `playtime` int(11) NOT NULL, `age` int(11) NOT NULL, `category` varchar(100) COLLATE utf8_bin NOT NULL, `author` varchar(100) COLLATE utf8_bin NOT NULL, `artist` varchar(100) COLLATE utf8_bin NOT NULL, `publisher` varchar(100) COLLATE utf8_bin NOT NULL, `publishdate` int(11) NOT NULL, `img1` varchar(500) COLLATE utf8_bin NOT NULL, `img2` varchar(500) COLLATE utf8_bin NOT NULL, `img3` varchar(500) COLLATE utf8_bin NOT NULL, `language` varchar(100) COLLATE utf8_bin NOT NULL, `gewicht` int(11) NOT NULL, `afmetingen` varchar(100) COLLATE utf8_bin [...]
MySQL meldt: Documentatie
#1146 - Table 'webshop.bg' doesn't exist
Toen gaf hij ook nog deze log:
Code (php)
1
2013-10-10 18:52:57 2936 [Warning] InnoDB: Cannot open table webshop/bg from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
Ik zit met de handen in het haar en hoop echt dat jullie me zullen kunnen helpen.
Veel dank bij voorbaat
Louis
webshop.bg repair Error Table 'webshop.bg' doesn't exist
webshop.bg repair status Operation failed
Bestaat er nog een andere manier om dit probleem op te lossen?