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
DB created with FB 1.5.x and used with FB 2.x leads to "index page error" [CORE2325] #2749
Comments
Commented by: @hvlad FB 2.x can't corrupt database just because it was created by FB 1.5.x How could you reproduce corruption ? Do you have some application wich made something with database and it became corrupted ? |
Commented by: Attila Molnár (e_pluribus_unum) I've got the original DB which was created on FB1.5.x (ODS 10.1). The gfix does not report error, and the queries run fine. |
Commented by: @hvlad Could you give to me for analyze ? |
Commented by: Attila Molnár (e_pluribus_unum) Hi! You can download the neccessary files and instructions from the following link : Hope it helps. |
Commented by: @dyemanov Vlad, was it reproducible? If so, were you able to track the issue down? |
Modified by: @dyemanovassignee: Vlad Khorsun [ hvlad ] |
Commented by: @hvlad Will try it today. I don't remember if i tried it in february ;) |
Commented by: @hvlad Confirmed. Looks as a bug in FB 2.x working with ODS 10 databases. Tried with current FB 2.0.6 |
Commented by: Attila Molnár (e_pluribus_unum) Hi! I reviewed my all reports, and I noticed, that this can be related to CORE2649. (different NULL key encoding by FB 1.5 and FB 2.x for ODS10 and WIN1250) |
You can close this issue. Thank you. |
Submitted by: Attila Molnár (e_pluribus_unum)
Votes: 1
The engine does not throw error, just the queries become very slow (because the index corruption) .The index page error is reported by gfix with -m parameter.
I can reproduce this bug. Unforunetly this means thousands of DDL, DML and DQL sql statements. How can I log all the sql statement?
The text was updated successfully, but these errors were encountered: