Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2.6, 10.2.8, 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL)
-
Windows 10 Home 64bit
-
10.2.10, 5.5.58
Description
Partitions get corrupted: internal error 160.
Unable to repair (with Alter table).
Symptom: The AutoIncrement value goes wild (from a few thousand, to numbers with 20+ digits).
Viewing an allegedly uncorrupted partition shows extremely distorted data.
Fault appears to follow adding a new partition (partitions by date) although the new
partition is for a future date, so not yet used.
Only fix discovered, so far, is to drop the table.
Not yet isolated the exact trigger.
Tables schema: ARIA ROW_FORMAT=PAGE TRANSACTIONAL=1 PAGE_CHECKSUM=1
(FYI: same application code using MyISAM does not fail)
What causes internal error 160?