Subject | Re: [firebird-support] Consistency Check When Backing Up |
---|---|
Author | Kurt Federspiel |
Post date | 2008-12-09T22:30:40Z |
Thanks, Alan & Dmitry.
Can anyone tell me WHY this happens? Is Dmitry correct that it is a hardware issue?
Thanks again.
Kurt.
________________________________
From: Alan McDonald <alan@...>
To: firebird-support@yahoogroups.com
Sent: Tuesday, December 9, 2008 11:53:23 AM
Subject: RE: [firebird-support] Consistency Check When Backing Up
connections to the server are current.
Then check the switches for gbak (ignoring whatever) and try them
If they still don't do anything, your best bet is to make another shell of
the database (make a metadata backup - this should work) and create this
shell. Then use a datapump (several available) to pump the data in all
tables to the new shell.
Alan
[Non-text portions of this message have been removed]
Can anyone tell me WHY this happens? Is Dmitry correct that it is a hardware issue?
Thanks again.
Kurt.
________________________________
From: Alan McDonald <alan@...>
To: firebird-support@yahoogroups.com
Sent: Tuesday, December 9, 2008 11:53:23 AM
Subject: RE: [firebird-support] Consistency Check When Backing Up
> Greets:First, don't move the file or try to use it further. Copy it while no
>
> I get the following error when attempting to back up:
> gbak: writing data for table EVENTS
> gbak: ERROR:internal gds software consistency check (decompression
> overran buffer (179), file: sqz.cpp line: 222)
> gbak: ERROR: gds_$receive failed
> gbak: Exiting before completion due to errors
> gbak: ERROR:internal gds software consistency check (can't continue
> after bugcheck)
>
>
> Can anyone tell me the cause of this? It appears to happen regularly
> on this one system; I am starting to wonder if it is a Disk issue.
>
> Is it possible to repair the DB and extract the data from it? We need
> the data to verify work.
>
> Thanks in advance.
> Kurt.
connections to the server are current.
Then check the switches for gbak (ignoring whatever) and try them
If they still don't do anything, your best bet is to make another shell of
the database (make a metadata backup - this should work) and create this
shell. Then use a datapump (several available) to pump the data in all
tables to the new shell.
Alan
[Non-text portions of this message have been removed]