Corrupt database file
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the shown SELECT queries against the imported database and inspect the reported DuckDB corrupt database file error at block location 359883091968. Trace the MySQL-to-AliSQL import path to determine how the checksum mismatch can occur; done means documenting a confirmed cause and a practical resolution or prevention procedure.
Written by the indexing model from the issue text.
Description
Import MySQL data into AliSQL. During queries, some data files were found to be corrupted. The query statement is as follows:
root[database]> select count() from h_record where time > '2025-04-01' and time < '2025-04-10';
+----------+
| count() |
+----------+
| 3061512 |
+----------+
1 row in set (0.02 sec)
root[database]> select count() from h_record where time > '2025-04-11' and time < '2025-04-12';
ERROR 7501 (HY000): [DuckDB] IO Error: Corrupt database file: computed checksum 7085340976184504599 does not match stored checksum 6666362943038018993 in block at location 359883091968.
root[database]> select count() from h_record where time > '2025-04-12' and time < '2025-04-13';
ERROR 7501 (HY000): [DuckDB] IO Error: Corrupt database file: computed checksum 7085340976184504599 does not match stored checksum 6666362943038018993 in block at location 359883091968.
How does this kind of problem occur, and how to resolve or prevent it?
- Dominant language
- C++
- Stars
- 6k
- Forks
- 902
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from alibaba/AliSQL
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·