Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Critical
-
Resolution: Unresolved
-
10.2.43, 11.6.1, 10.6, 10.11, 11.4, 11.8, 10.5(EOL), 11.8.2
-
None
-
WIndows 11
-
Q4/2025 Server Maintenance
Description
FYI:
Having a unit test that creates an Aria table, populates some rows and then deletes one of the rows, where the DELETE fails in error: '126 "Index is corrupted"'.
The unit test runs OK on MariaDB (Community Server) V11.4.5 but fails on V11.8.2.
The table creation clause is:
CREATE TABLE iccl ( |
id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY COMMENT 'Primary id', |
i_datsetid VARCHAR(100) NOT NULL COMMENT 'Data set ID', |
system_id TINYINT UNSIGNED NOT NULL COMMENT 'Reference to id in SYSTEM table', |
part_id INT NOT NULL COMMENT 'Reference to id in PART table', |
i_dateeffe INT NOT NULL COMMENT 'Date effective', |
i_timeeffe BIGINT(12) NOT NULL COMMENT 'Time effective', |
i_newvalue DECIMAL(20,2) NOT NULL COMMENT 'New value', |
i_usercod1 VARCHAR(16) COMMENT 'User defined code 1', |
i_usercod2 VARCHAR(16) COMMENT 'User defined code 2', |
i_usercod3 VARCHAR(16) COMMENT 'User defined code 3', |
i_usercod4 VARCHAR(16) COMMENT 'User defined code 4', |
i_usercod5 VARCHAR(16) COMMENT 'User defined code 5', |
business_day CHAR(8) NOT NULL COMMENT 'Business day', |
transaction_link_id VARCHAR(100) COMMENT 'Transaction link ID', |
order_type VARCHAR(10) COMMENT 'Type of the iccl order', |
entry_date INT COMMENT 'Entry date', |
entry_time BIGINT(12) COMMENT 'Entry time', |
revocation_date INT COMMENT 'Revocation date', |
revocation_time BIGINT(12) COMMENT 'Revocation time', |
modified TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT 'Last modified time stamp', |
INDEX idx_iccl_bus_day (business_day), |
UNIQUE unq_iccl (id, i_datsetid, system_id, part_id, business_day) |
) ENGINE=Aria;
|
The DELETE clause is:
DELETE FROM iccl WHERE system_id = ? AND i_datsetid = ? |
where the parameters are properly provided. As you can see the DELETE clause does not match with any of the table's indexes, but it should not be a problem.
The database is not set to use transactionality thus COMMIT clause is not used.