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

DB created with FB 1.5.x and used with FB 2.x leads to "index page error" [CORE2325] #2749

Closed
firebird-automations opened this issue Feb 16, 2009 · 10 comments

Comments

@firebird-automations
Copy link
Collaborator

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?

@firebird-automations
Copy link
Collaborator Author

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 ?
Why do yo know it was not already corrupted long time before ?

@firebird-automations
Copy link
Collaborator Author

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.
After running a subprocess of the application the gfix report the error. I'm using the DB with FB2.0.5.
The subprocess is responsible for the database structure. It compares the actual structure with the desired and makes the neccessary changes if needed (create/alter table/index/storedproc/views/triggers/domains/checks, insert/delete/alter records, etc.)

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Could you give to me for analyze
- original (not corrupted) database
- application
- instruction how to reproduce corruption

?

@firebird-automations
Copy link
Collaborator Author

Commented by: Attila Molnár (e_pluribus_unum)

Hi!

You can download the neccessary files and instructions from the following link :
ftp://firebirdproject:projectfirebird@ftp.mve.hu/testcase.zip

Hope it helps.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Vlad, was it reproducible? If so, were you able to track the issue down?

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Will try it today. I don't remember if i tried it in february ;)

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Confirmed.

Looks as a bug in FB 2.x working with ODS 10 databases.
After i upgraded database up to ODS 11 bug is not reproduced anymore.

Tried with current FB 2.0.6

@firebird-automations
Copy link
Collaborator Author

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)

@EPluribusUnum
Copy link

You can close this issue. Thank you.

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

No branches or pull requests

3 participants