Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Schema index checksum mismatch found! #862

Closed
fazi1058 opened this issue Oct 24, 2022 · 6 comments · Fixed by #877 or #909
Closed

[BUG] Schema index checksum mismatch found! #862

fazi1058 opened this issue Oct 24, 2022 · 6 comments · Fixed by #877 or #909
Labels

Comments

@fazi1058
Copy link

Hello!
I am using myloader and mydumper for taking bakup and restore them.But when I restore backup I encounter with errors below:

** (myloader:2868268): WARNING **: 10:04:25.349: Schema index checksum mismatch found for `db_name`.`orders`. Got '83671d4e', expecting 'CB0C64DE' in file: db_name.orders-schema-indexes-checksum

** (myloader:2868268): WARNING **: 10:04:24.369: Schema index checksum mismatch found for `db_name`.`demo__orders`. Got '40fd4431', expecting '160AD7C6' in file: db_name.demo__orders-schema-indexes-checksum

My question is that : Should I be worried? because all checksum for data and their schema was OK except these two! How does it effect? How it is happening?

mydmper command:

mydumper --database=$DB_NAME --user=$DB_USER --outputdir=/Backup/$DB_NAME--$DATE --build-empty-files --trx-consistency-only --compress --checksum-all

myloader command:

myloader -t 32 -d db_name --serialized-table-creation --verbose 3 -B db_name

@fazi1058 fazi1058 added the bug label Oct 24, 2022
@davidducos
Copy link
Member

Hi @fazi1058, can you share the SHOW CREATE TABLE from the database you exported and the database you imported?

@davidducos davidducos added this to the Release 0.13.1-1 milestone Oct 26, 2022
@fazi1058
Copy link
Author

fazi1058 commented Nov 1, 2022

I am afraid I can't share table structure with you but when I ran query the only difference between them was auto_increment:

< ) ENGINE=InnoDB AUTO_INCREMENT=587030163 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci |
---
> ) ENGINE=InnoDB AUTO_INCREMENT=615939773 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci |

first one belongs to the database I imported and second one belongs to database I got export from.

@davidducos
Copy link
Member

Can you execute this on both databases:
select table_name,INDEX_NAME,SEQ_IN_INDEX,COLUMN_NAME from information_schema.STATISTICS WHERE table_schema='<database>' AND table_name='<table>';

With the right <database> and <table> values?

@davidducos
Copy link
Member

Definitely this is a duplicate of #860, sorry for the back and forth...

@davidducos
Copy link
Member

It is still not working properly

@davidducos
Copy link
Member

@fazi1058 please, share a test case so I can work on this before the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants