Bug #106868 InnoDB: Assertion failure in thread 9560 in file trx0purge.cc line 699
Submitted: 30 Mar 2022 4:22 Modified: 30 Mar 2022 13:09
Reporter: Joel Stephanas Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.6.17 OS:Windows (win10)
Assigned to: CPU Architecture:x86

[30 Mar 2022 4:22] Joel Stephanas
Description:
I really need help so urgent.

Error report :

2022-03-30 05:50:08 11184 [Note] Plugin 'FEDERATED' is disabled.
2022-03-30 05:50:08 11184 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-03-30 05:50:08 11184 [Note] InnoDB: The InnoDB memory heap is disabled
2022-03-30 05:50:08 11184 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-03-30 05:50:08 11184 [Note] InnoDB: Compressed tables use zlib 1.2.3
2022-03-30 05:50:08 11184 [Note] InnoDB: Not using CPU crc32 instructions
2022-03-30 05:50:08 11184 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2022-03-30 05:50:08 11184 [Note] InnoDB: Completed initialization of buffer pool
2022-03-30 05:50:08 11184 [Note] InnoDB: Highest supported file format is Barracuda.
2022-03-30 05:50:08 11184 [Note] InnoDB: The log sequence numbers 393967677 and 393967677 in ibdata files do not match the log sequence number 394786623 in the ib_logfiles!
2022-03-30 05:50:08 11184 [Note] InnoDB: Database was not shutdown normally!
2022-03-30 05:50:08 11184 [Note] InnoDB: Starting crash recovery.
2022-03-30 05:50:08 11184 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-03-30 05:50:08 11184 [Note] InnoDB: Restoring possible half-written data pages 
2022-03-30 05:50:08 11184 [Note] InnoDB: from the doublewrite buffer...
2022-03-30 05:50:09 11184 [Note] InnoDB: 128 rollback segment(s) are active.
2022-03-30 05:50:09 11184 [Note] InnoDB: Waiting for purge to start
2022-03-30 05:50:09 1ac  InnoDB: Assertion failure in thread 428 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
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.
2022-03-30 05:50:09 11184 [Note] InnoDB: 5.6.17 started; log sequence number 394786623
2022-03-30 05:50:09 11184 [Note] Server hostname (bind-address): '*'; port: 3306
2022-03-30 05:50:09 11184 [Note] IPv6 is available.
2022-03-30 05:50:09 11184 [Note]   - '::' resolves to '::';
2022-03-30 05:50:09 11184 [Note] Server socket created on IP: '::'.
2022-03-30 05:50:09 11184 [Note] Event Scheduler: Loaded 0 events
2022-03-30 05:50:09 11184 [Note] wampmysqld: ready for connections.
Version: '5.6.17'  socket: ''  port: 3306  MySQL Community Server (GPL)

How to repeat:
Start the service or at least back up the databases.
[30 Mar 2022 13:09] MySQL Verification Team
Hi Mr. Stephanas,

Thank you for your bug report.

However, MySQL 5.6 is off the maintenance for a long time.

If you get similar problems with latest release of 8.0, which is now a release  8.0.28, please let us know.

Unsupported.