Default not found: key:xxxx, maybe read truncated/dropped table data?

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: default not found: key:xxxx, maybe read truncated/dropped table data?

| username: wfxxh

[Test Environment for TiDB] Testing
[TiDB Version] v5.4.3
Without any operations, suddenly some tables cannot be fully scanned, reporting an error: default not found: key:xxxx, maybe read truncated/dropped table data?

Hardware server: 48 cores, 256GB memory

image

| username: 大飞哥online | Original post link

Looking at your screenshot, it seems that the error occurs after adding the order by clause, right?

| username: 啦啦啦啦啦 | Original post link

Refer to this post and take a look:

| username: wfxxh | Original post link

I read this post, but I didn’t enable enable-ttl.

| username: wfxxh | Original post link

A full table scan will result in an error, and the data cannot be exported.

| username: 啦啦啦啦啦 | Original post link

You don’t need to pay attention to the enable-ttl parameter. You can follow the steps in the above post for analysis.

| username: wfxxh | Original post link

There are no results after the analysis :cold_sweat:

There is no useful information in the logs, only errors reported during the query.

| username: cassblanca | Original post link

There are similar posts in the forum. It is caused by the enable-ttl parameter. You can refer to them for a solution.

| username: wfxxh | Original post link

Brother, I already said it.

| username: 有猫万事足 | Original post link

The causes might be different, but the symptoms are really similar.
Just look at this post and try fixing it accordingly.

| username: wfxxh | Original post link

Brother, I followed these steps to analyze it, but there were no results…

| username: 有猫万事足 | Original post link

Is it that the store cannot be found based on this key?
Or did you find it and followed the steps but it had no effect?
Please provide some details.
Otherwise, no one will know how to help you.

| username: redgame | Original post link

You can try to repair the table using REPAIR TABLE.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.