mysql error

Problems with the Windows version of XAMPP, questions, comments, and anything related.

mysql error

Postby isrivastava » 04. November 2013 20:26

i am new , and i have no idea why my sql has errors please help. Thanks





2013-10-03 15:43:20 4028 [Note] Plugin 'FEDERATED' is disabled.
2013-10-03 15:43:20 1adc 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-03 15:43:20 4028 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-03 15:43:20 4028 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-03 15:43:20 4028 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-03 15:43:20 4028 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-03 15:43:20 4028 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-03 15:43:20 4028 [Note] InnoDB: Completed initialization of buffer pool
2013-10-03 15:43:20 4028 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-10-03 15:43:20 4028 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-10-03 15:43:20 4028 [Note] InnoDB: Database physically writes the file full: wait...
2013-10-03 15:43:21 4028 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-10-03 15:43:21 4028 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-10-03 15:43:21 4028 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-10-03 15:43:21 4028 [Warning] InnoDB: New log files created, LSN=45781
2013-10-03 15:43:21 4028 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-10-03 15:43:21 4028 [Note] InnoDB: Doublewrite buffer created
2013-10-03 15:43:21 4028 [Note] InnoDB: 128 rollback segment(s) are active.
2013-10-03 15:43:21 4028 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-10-03 15:43:21 4028 [Note] InnoDB: Foreign key constraint system tables created
2013-10-03 15:43:21 4028 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-10-03 15:43:21 4028 [Note] InnoDB: Tablespace and datafile system tables created.
2013-10-03 15:43:21 4028 [Note] InnoDB: Waiting for purge to start
2013-10-03 15:43:21 4028 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-10-03 15:43:22 4028 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 6ebcf2ed-2c14-11e3-a24b-f8d0295b4d70.
2013-10-03 15:43:22 4028 [Note] Server hostname (bind-address): '*'; port: 3306
2013-10-03 15:43:22 4028 [Note] IPv6 is available.
2013-10-03 15:43:22 4028 [Note] - '::' resolves to '::';
2013-10-03 15:43:22 4028 [Note] Server socket created on IP: '::'.
2013-10-03 15:43:22 4028 [Warning] InnoDB: Cannot open table mysql/slave_master_info 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.
2013-10-03 15:43:22 4028 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-10-03 15:43:22 4028 [Warning] InnoDB: Cannot open table mysql/slave_worker_info 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.
2013-10-03 15:43:22 4028 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info 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.
2013-10-03 15:43:22 4028 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-10-03 15:43:22 4028 [Note] Event Scheduler: Loaded 0 events
2013-10-03 15:43:22 4028 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-10-03 16:15:25 710 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:15:25 710 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:15:25 710 InnoDB: Error: Fetch of persistent statistics requested for table "webservice"."users" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-03 16:19:17 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:19:17 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:19:17 1e24 InnoDB: Error: Fetch of persistent statistics requested for table "webservice"."comments" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-03 16:20:19 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:20:19 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:20:19 1e242013-10-03 16:20:19 4028 [Warning] Invalid (old?) table or database name '#sql-fbc_48'
InnoDB: Error: Fetch of persistent statistics requested for table "webservice".<result 2 when explaining filename '#sql-fbc_48'> but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-03 16:20:19 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:20:19 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:20:19 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:20:19 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:20:19 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:20:19 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:20:19 1e24 InnoDB: Error: Fetch of persistent statistics requested for table "webservice"."users" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-03 16:20:44 1e24 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-03 16:20:44 1e24 InnoDB: Error: Fetch of persistent statistics requested for table "webservice"."users" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-10-10 16:24:46 7132 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 16:24:46 184c 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 16:24:46 7132 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 16:24:46 7132 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 16:24:46 7132 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 16:24:46 7132 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 16:24:46 7132 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 16:24:46 7132 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 16:24:46 7132 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 16:24:46 7132 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 16:24:46 7132 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 16:24:46 7132 [Note] InnoDB: Starting crash recovery.
2013-10-10 16:24:46 7132 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 16:24:46 7132 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 16:24:52 6496 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 16:24:52 1b80 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 16:24:52 6496 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 16:24:52 6496 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 16:24:52 6496 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 16:24:52 6496 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 16:24:52 6496 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 16:24:52 6496 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 16:24:52 6496 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 16:24:52 6496 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 16:24:52 6496 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 16:24:52 6496 [Note] InnoDB: Starting crash recovery.
2013-10-10 16:24:52 6496 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 16:24:52 6496 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 16:25:14 6592 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 16:25:14 568 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 16:25:14 6592 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 16:25:14 6592 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 16:25:14 6592 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 16:25:14 6592 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 16:25:14 6592 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 16:25:14 6592 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 16:25:14 6592 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 16:25:14 6592 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 16:25:14 6592 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 16:25:14 6592 [Note] InnoDB: Starting crash recovery.
2013-10-10 16:25:14 6592 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 16:25:14 6592 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 16:25:18 6508 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 16:25:18 d50 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 16:25:18 6508 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 16:25:18 6508 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 16:25:18 6508 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 16:25:18 6508 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 16:25:18 6508 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 16:25:18 6508 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 16:25:18 6508 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 16:25:18 6508 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 16:25:18 6508 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 16:25:18 6508 [Note] InnoDB: Starting crash recovery.
2013-10-10 16:25:18 6508 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 16:25:18 6508 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 16:50:37 8088 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 16:50:37 e38 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 16:50:37 8088 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 16:50:37 8088 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 16:50:37 8088 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 16:50:37 8088 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 16:50:37 8088 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 16:50:37 8088 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 16:50:37 8088 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 16:50:37 8088 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 16:50:37 8088 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 16:50:37 8088 [Note] InnoDB: Starting crash recovery.
2013-10-10 16:50:37 8088 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 16:50:37 8088 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 16:52:18 3220 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 16:52:18 17cc 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 16:52:18 3220 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 16:52:18 3220 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 16:52:18 3220 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 16:52:18 3220 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 16:52:18 3220 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 16:52:18 3220 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 16:52:18 3220 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 16:52:18 3220 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 16:52:18 3220 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 16:52:18 3220 [Note] InnoDB: Starting crash recovery.
2013-10-10 16:52:18 3220 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 16:52:18 3220 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 16:52:24 7604 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 16:52:24 aac 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 16:52:24 7604 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 16:52:24 7604 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 16:52:24 7604 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 16:52:24 7604 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 16:52:24 7604 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 16:52:24 7604 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 16:52:24 7604 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 16:52:24 7604 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 16:52:24 7604 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 16:52:24 7604 [Note] InnoDB: Starting crash recovery.
2013-10-10 16:52:24 7604 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 16:52:24 7604 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 16:56:13 2024 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 16:56:13 11bc 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 16:56:13 2024 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 16:56:13 2024 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 16:56:13 2024 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 16:56:13 2024 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 16:56:13 2024 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 16:56:13 2024 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 16:56:13 2024 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 16:56:13 2024 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 16:56:13 2024 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 16:56:13 2024 [Note] InnoDB: Starting crash recovery.
2013-10-10 16:56:13 2024 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 16:56:13 2024 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 17:03:21 7596 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 17:03:21 880 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 17:03:21 7596 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 17:03:21 7596 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 17:03:21 7596 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 17:03:21 7596 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 17:03:21 7596 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 17:03:21 7596 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 17:03:21 7596 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 17:03:21 7596 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 17:03:21 7596 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 17:03:21 7596 [Note] InnoDB: Starting crash recovery.
2013-10-10 17:03:21 7596 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 17:03:21 7596 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 17:23:14 7968 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 17:23:14 1570 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 17:23:14 7968 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 17:23:14 7968 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 17:23:14 7968 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 17:23:14 7968 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 17:23:14 7968 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 17:23:14 7968 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 17:23:14 7968 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 17:23:14 7968 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 17:23:14 7968 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 17:23:14 7968 [Note] InnoDB: Starting crash recovery.
2013-10-10 17:23:14 7968 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 17:23:14 7968 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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 17:23:33 7664 [Note] Plugin 'FEDERATED' is disabled.
2013-10-10 17:23:33 16fc 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 17:23:33 7664 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 17:23:33 7664 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-10 17:23:33 7664 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 17:23:33 7664 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 17:23:33 7664 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-10 17:23:33 7664 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 17:23:33 7664 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-10 17:23:33 7664 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-10-10 17:23:33 7664 [Note] InnoDB: Database was not shutdown normally!
2013-10-10 17:23:33 7664 [Note] InnoDB: Starting crash recovery.
2013-10-10 17:23:33 7664 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-10 17:23:33 7664 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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-11-05 00:42:34 1592 [Note] Plugin 'FEDERATED' is disabled.
2013-11-05 00:42:34 1db4 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-11-05 00:42:34 1592 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-05 00:42:34 1592 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-05 00:42:34 1592 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-05 00:42:34 1592 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-05 00:42:34 1592 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-05 00:42:34 1592 [Note] InnoDB: Completed initialization of buffer pool
2013-11-05 00:42:34 1592 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-05 00:42:34 1592 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1620785 in the ib_logfiles!
2013-11-05 00:42:34 1592 [Note] InnoDB: Database was not shutdown normally!
2013-11-05 00:42:34 1592 [Note] InnoDB: Starting crash recovery.
2013-11-05 00:42:34 1592 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-05 00:42:35 1592 [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 webservice/comments which uses space ID: 2 at filepath: .\webservice\comments.ibd
InnoDB: Error: could not open single-table tablespace file .\webservice\comments.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.
isrivastava
 
Posts: 1
Joined: 04. November 2013 20:17
Operating System: windows 7

Re: mysql error

Postby Altrea » 05. November 2013 05:28

We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 8298
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 61 guests