RE: [firebird-support] Database/Table Corruption
Hi Mark. I decided to "pump" all tables, except the one that was inconsistent, from the old to a new database. After this, I extracted all records I could from the incosistent table and inserted into the new database. Possibly I lost some records from this table, I realy don´t know, because "select count(id) from mytable" results in the same " ERROR:internal Firebird consistency check (decompression overran buffer (179), file: sqz.cpp line: 239)" Atenciosamente, + + Hugo Eyng + + De: firebird-support@yahoogroups.com em nome de Mark Rotteveel m...@lawinegevaar.nl [firebird-support] Enviado: quarta-feira, 1 de janeiro de 2020 08:25 Para: firebird-support@yahoogroups.com Assunto: Re: [firebird-support] Database/Table Corruption On 31/12/2019 18:27, Hugo Eyng hugoe...@msn.com [firebird-support] wrote: > Gfix didn´t work even using it as you explained. Please be more specific than "didn't work". What happened, did you get an error, did gfix find nothing wrong? What was the gfix output? Mark -- Mark Rotteveel
Re: [firebird-support] Database/Table Corruption
On 31/12/2019 18:27, Hugo Eyng hugoe...@msn.com [firebird-support] wrote: > Gfix didn´t work even using it as you explained. Please be more specific than "didn't work". What happened, did you get an error, did gfix find nothing wrong? What was the gfix output? Mark -- Mark Rotteveel
Re: [firebird-support] Database/Table Corruption
Shutdown firebird, copy the database to a new file copy.
Then start firebird and try the backup and restore process on the file copy..
Sent from Yahoo Mail for iPhone
On Tuesday, December 31, 2019, 12:29 PM, Hugo Eyng hugoe...@msn.com
[firebird-support] wrote:
Hello Alexey.
IBPump was a good idea.
IBPump doesn´t recover the corrupted table but at least it is possible to
restore all others.
Atenciosamente,
+ + Hugo Eyng + +
De: firebird-support@yahoogroups.com em nome
de Alexey Kovyazin a...@ib-aid.com [firebird-support]
Enviado: sábado, 28 de dezembro de 2019 07:33
Para: firebird-support@yahoogroups.com
Assunto: Re: [firebird-support] Database/Table Corruption
Hello,
before you try FirstAID, download IBPump and try to pump all data to the new
database with the same structure.
Regards,
Alexey Kovyazin
IBSurgeon
On 27.12.2019 22:49, Hugo Eyng hugoe...@msn.com [firebird-support] wrote:
Hello.
FB 2.5.7Windows 10 64 bitsPage size 4096
I am facing some dificulties to backup and restore a corrupted DB. I searched
the Internet to find some help and tried everthing I read.
I already tried "gfix -full - mend" and did not work.
gbak -B -V -user SYSDBA -password masterkey MYDB.FDB MYDB..FBK
...
gbak:46 records written
gbak: ERROR:internal Firebird consistency check (decompression overran buffer
(179), file: sqz.cpp line: 239)
gbak: ERROR:gds_$receive failed
gbak:Exiting before completion due to errors
gbak: ERROR:internal Firebird consistency check (can't continue after bugcheck)
I already dropped the table that causes this message but than the error occurs
ahead.
..
gbak:writing table constraints
gbak:writing constraint INTEG_1
gbak:writing constraint INTEG_2
gbak:writing constraint INTEG_3
gbak:writing constraint INTEG_4
gbak:writing constraint INTEG_5
gbak:writing constraint INTEG_6
gbak:writing constraint INTEG_7
gbak:writing constraint INTEG_8
gbak:writing constraint INTEG_9
gbak:writing constraint INTEG_10
gbak:writing constraint INTEG_11
gbak:writing constraint INTEG_12
gbak:writing constraint INTEG_13
gbak:writing constraint INTEG_14
gbak:writing constraint INTEG_15
gbak:writing constraint INTEG_16
gbak:writing constraint INTEG_17
gbak: ERROR:internal Firebird consistency check (decompression overran buffer
(179), file: sqz.cpp line: 239)
gbak:Exiting before completion due to errors
gbak: ERROR:internal Firebird consistency check (can't continue after bugcheck)
Any help will be apreciated.
Atenciosamente,
+ + Hugo Eyng + +
#yiv2871085108 #yiv2871085108 -- #yiv2871085108ygrp-mkp {border:1px solid
#d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv2871085108
#yiv2871085108ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv2871085108
#yiv2871085108ygrp-mkp #yiv2871085108hd
{color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px
0;}#yiv2871085108 #yiv2871085108ygrp-mkp #yiv2871085108ads
{margin-bottom:10px;}#yiv2871085108 #yiv2871085108ygrp-mkp .yiv2871085108ad
{padding:0 0;}#yiv2871085108 #yiv2871085108ygrp-mkp .yiv2871085108ad p
{margin:0;}#yiv2871085108 #yiv2871085108ygrp-mkp .yiv2871085108ad a
{color:#ff;text-decoration:none;}#yiv2871085108 #yiv2871085108ygrp-sponsor
#yiv2871085108ygrp-lc {font-family:Arial;}#yiv2871085108
#yiv2871085108ygrp-sponsor #yiv2871085108ygrp-lc #yiv2871085108hd {margin:10px
0px;font-weight:700;font-size:78%;line-height:122%;}#yiv2871085108
#yiv2871085108ygrp-sponsor #yiv2871085108ygrp-lc .yiv2871085108ad
{margin-bottom:10px;padding:0 0;}#yiv2871085108 #yiv2871085108actions
{font-family:Verdana;font-size:11px;padding:10px 0;}#yiv2871085108
#yiv2871085108activity
{background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv2871085108
#yiv2871085108activity span {font-weight:700;}#yiv2871085108
#yiv2871085108activity span:first-child
{text-transform:uppercase;}#yiv2871085108 #yiv2871085108activity span a
{color:#5085b6;text-decoration:none;}#yiv2871085108 #yiv2871085108activity span
span {color:#ff7900;}#yiv2871085108 #yiv2871085108activity span
.yiv2871085108underline {text-decoration:underline;}#yiv2871085108
.yiv2871085108attach
{clear:both;display:table;font-family:Arial;font-size:12px;padding:10px
0;width:400px;}#yiv2871085108 .yiv2871085108attach div a
{text-decoration:none;}#yiv2871085108 .yiv2871085108attach img
{border:none;padding-right:5px;}#yiv2871085108 .yiv2871085108attach label
{display:block;margin-bottom:5px;}#yiv2871085108 .yiv2871085108attach label a
{text-decoration:none;}#yiv2871085108 blockquote {margin:0 0 0
4px;}#yiv2871085108 .yiv2871085108bold
{font-family:Arial;font-size:13px;font-weight:700;}#yiv2871085108
.yiv2871085108bold a {text-decoration:none;}#yiv2871085108 dd.yiv2871085108last
p a {font-family:Verdana;font-weight:700;}#yiv2871085108 dd.yiv2871085108last p
span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv2871085108
dd.yiv287108
RE: [firebird-support] Database/Table Corruption
Hello Alexey. IBPump was a good idea. IBPump doesn´t recover the corrupted table but at least it is possible to restore all others. Atenciosamente, + + Hugo Eyng + + De: firebird-support@yahoogroups.com em nome de Alexey Kovyazin a...@ib-aid.com [firebird-support] Enviado: sábado, 28 de dezembro de 2019 07:33 Para: firebird-support@yahoogroups.com Assunto: Re: [firebird-support] Database/Table Corruption Hello, before you try FirstAID, download IBPump and try to pump all data to the new database with the same structure. Regards, Alexey Kovyazin IBSurgeon On 27.12.2019 22:49, Hugo Eyng hugoe...@msn.com<mailto:hugoe...@msn.com> [firebird-support] wrote: Hello. FB 2.5.7 Windows 10 64 bits Page size 4096 I am facing some dificulties to backup and restore a corrupted DB. I searched the Internet to find some help and tried everthing I read. I already tried "gfix -full - mend" and did not work. gbak -B -V -user SYSDBA -password masterkey MYDB.FDB MYDB.FBK . .. .. . gbak:46 records written gbak: ERROR:internal Firebird consistency check (decompression overran buffer (179), file: sqz.cpp line: 239) gbak: ERROR:gds_$receive failed gbak:Exiting before completion due to errors gbak: ERROR:internal Firebird consistency check (can't continue after bugcheck) I already dropped the table that causes this message but than the error occurs ahead. . .. .. gbak:writing table constraints gbak:writing constraint INTEG_1 gbak:writing constraint INTEG_2 gbak:writing constraint INTEG_3 gbak:writing constraint INTEG_4 gbak:writing constraint INTEG_5 gbak:writing constraint INTEG_6 gbak:writing constraint INTEG_7 gbak:writing constraint INTEG_8 gbak:writing constraint INTEG_9 gbak:writing constraint INTEG_10 gbak:writing constraint INTEG_11 gbak:writing constraint INTEG_12 gbak:writing constraint INTEG_13 gbak:writing constraint INTEG_14 gbak:writing constraint INTEG_15 gbak:writing constraint INTEG_16 gbak:writing constraint INTEG_17 gbak: ERROR:internal Firebird consistency check (decompression overran buffer (179), file: sqz.cpp line: 239) gbak:Exiting before completion due to errors gbak: ERROR:internal Firebird consistency check (can't continue after bugcheck) Any help will be apreciated. Atenciosamente, + + Hugo Eyng + +
RE: [firebird-support] Database/Table Corruption
Hello Mark. Gfix didn´t work even using it as you explained. Atenciosamente, + + Hugo Eyng + + De: firebird-support@yahoogroups.com em nome de Mark Rotteveel m...@lawinegevaar.nl [firebird-support] Enviado: sábado, 28 de dezembro de 2019 07:02 Para: firebird-support@yahoogroups.com Assunto: Re: [firebird-support] Database/Table Corruption On 27/12/2019 20:49, Hugo Eyng hugoe...@msn.com [firebird-support] wrote: > FB 2.5.7 > Windows 10 64 bits > Page size 4096 I'd suggest upgrading to 2.5.9 and see if that fixes the problem. Both in 2.5.8 and 2.5.9, bugs with gbak were fixed. Those bug fixes don't match the description of this problem, but it never hurts to try with a newer version. > I am facing some dificulties to backup and restore a corrupted DB. I > searched the Internet to find some help and tried everthing I read. > > I already tried "gfix -full - mend" and did not work. It should be -mend, not - mend. However, did you read all the caveats about using -mend in the gfix documentation[1] as it can cause loss of data? However, did gfix output any information about problems? Preferably start with gfix -validate -full -no_update then move to gfix -validate -full and only use gfix -mend as a last resort (and make a copy of the database before running it!). [1]: https://firebirdsql.org/file/documentation/reference_manuals/user_manuals/html/gfix-dbverify.html -- Mark Rotteveel
Re: [firebird-support] Database/Table Corruption
Hello, before you try FirstAID, download IBPump and try to pump all data to the new database with the same structure. Regards, Alexey Kovyazin IBSurgeon On 27.12.2019 22:49, Hugo Eyng hugoe...@msn.com [firebird-support] wrote: Hello. FB 2.5.7 Windows 10 64 bits Page size 4096 I am facing some dificulties to backup and restore a corrupted DB. I searched the Internet to find some help and tried everthing I read. I already tried "gfix -full - mend" and did not work. gbak -B -V -user SYSDBA -password masterkey MYDB.FDB MYDB.FBK . . gbak:46 records written gbak: ERROR:internal Firebird consistency check (decompression overran buffer (179), file: sqz.cpp line: 239) gbak: ERROR:gds_$receive failed gbak:Exiting before completion due to errors gbak: ERROR:internal Firebird consistency check (can't continue after bugcheck) I already dropped the table that causes this message but than the error occurs ahead. ... . . gbak:writing table constraints gbak:writing constraint INTEG_1 gbak:writing constraint INTEG_2 gbak:writing constraint INTEG_3 gbak:writing constraint INTEG_4 gbak:writing constraint INTEG_5 gbak:writing constraint INTEG_6 gbak:writing constraint INTEG_7 gbak:writing constraint INTEG_8 gbak:writing constraint INTEG_9 gbak:writing constraint INTEG_10 gbak:writing constraint INTEG_11 gbak:writing constraint INTEG_12 gbak:writing constraint INTEG_13 gbak:writing constraint INTEG_14 gbak:writing constraint INTEG_15 gbak:writing constraint INTEG_16 gbak:writing constraint INTEG_17 gbak: ERROR:internal Firebird consistency check (decompression overran buffer (179), file: sqz.cpp line: 239) gbak:Exiting before completion due to errors gbak: ERROR:internal Firebird consistency check (can't continue after bugcheck) Any help will be apreciated. Atenciosamente, + + Hugo Eyng + +
Re: [firebird-support] Database/Table Corruption
On 27/12/2019 20:49, Hugo Eyng hugoe...@msn.com [firebird-support] wrote: > FB 2.5.7 > Windows 10 64 bits > Page size 4096 I'd suggest upgrading to 2.5.9 and see if that fixes the problem. Both in 2.5.8 and 2.5.9, bugs with gbak were fixed. Those bug fixes don't match the description of this problem, but it never hurts to try with a newer version. > I am facing some dificulties to backup and restore a corrupted DB. I > searched the Internet to find some help and tried everthing I read. > > I already tried "gfix -full - mend" and did not work. It should be -mend, not - mend. However, did you read all the caveats about using -mend in the gfix documentation[1] as it can cause loss of data? However, did gfix output any information about problems? Preferably start with gfix -validate -full -no_update then move to gfix -validate -full and only use gfix -mend as a last resort (and make a copy of the database before running it!). [1]: https://firebirdsql.org/file/documentation/reference_manuals/user_manuals/html/gfix-dbverify.html -- Mark Rotteveel
Re: [firebird-support] Database/Table Corruption
27.12.2019 20:49, Hugo Eyng hugoe...@msn.com [firebird-support] wrote: > Any help will be apreciated. http://www.ibphoenix.com/services/repair https://ib-aid.com/en/firebird-interbase-recovery-service/ -- WBR, SD. ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/firebird-support/join (Yahoo! ID required) <*> To change settings via email: firebird-support-dig...@yahoogroups.com firebird-support-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: firebird-support-unsubscr...@yahoogroups.com <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
