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

gfix validation problem [CORE5109] #5393

Closed
firebird-automations opened this issue Feb 9, 2016 · 6 comments
Closed

gfix validation problem [CORE5109] #5393

firebird-automations opened this issue Feb 9, 2016 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Attila Molnár (e_pluribus_unum)

Hi!

gfix -user sysdba -password masterkey d:\Databases\Szhely_hibas.gdb3s -validate
Summary of validation errors
Number of index page errors : 2

gfix -user sysdba -password masterkey d:\Databases\Szhely_hibas.gdb3s -v -full
Summary of validation errors

    Number of record level errors   : 1
    Number of index page errors     : 4
    Number of database page errors  : 352

gbak -user sysdba -password masterkey -b 127.0.0.1/3051:d:\Databases\Szhely_hibas.gdb3s d:\b.gbk
gbak: ERROR:Unable to complete network request to host "127.0.0.1".
gbak: ERROR: Error reading data from the connection.
gbak: ERROR:gds_$open_blob failed
gbak:Exiting before completion due to errors

-b is failed because of database page errors, I can accept that, but why "Number of index page errors" are different for the two validation?

Database : ftp:\\firebirdproject@ftp.mve.hu (I send password on reuqest in provate message)
PS.: Can you tell what caused the corruption?

Thank you!

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

> -b is failed because of database page errors

Probably, but not necessary

> why "Number of index page errors" are different for the two validation?

Full validation makes more checks.
firebird.log contains records for every found issue.

You may send pwd to me privately (to mailto:hvlad@users.sf.net)

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

This seems like a support issue. What is the development/tracker issue here?

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

I'm able to backup (using -g switch) and restore database with no problem.
With gc enabled engine is crashed, will investigate it a bit later.

PS FB 2.5.6

@firebird-automations
Copy link
Collaborator Author

Commented by: Omacht András (aomacht)

Hi Vlad,

yes, we could backup (with -g) and restore the databes too with 2.5.4. (It happened last week.)
There wasn't any sign of problems in the firebird.log file until the GC didn't start every time when we tried to connect to database.

<cut>
SERVER Thu Feb 4 09:00:04 2016
Sweep is started by SWEEPER
Database "....gdb3s"
OIT 14090742, OAT 14118168, OST 14118168, Next 14118169

SERVER Thu Feb 4 09:00:20 2016
Sweep is started by SWEEPER
Database "....gdb3s"
OIT 14090742, OAT 14118178, OST 14118178, Next 14118179
<cut>

According to the log this sweeper processes were never finished or died with error.

That gave us the idea to use gbak with -g.

(I think the problem is around the indicies of kt_rpttemp table.)

Thanks for investigating the problem.

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

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

1 participant