Subject | Re: [firebird-support] Restore error |
---|---|
Author | Helen Borrie |
Post date | 2005-08-14T06:37:01Z |
At 02:46 PM 14/08/2005 +1000, Grant Brown wrote:
eliminate the possibility that someone pulled out a plug, there's a
possibility the restore error cause the server to crash.
Can you make it happen again? and, if so, are you able to check whether
the Firebird server is still running after you see this message? It would
be useful to get closer to identifying what was happening when the invalid
decompression was detected.
Are you able to restore a metadata-only backup?
Which Fb 1.5 release are you running? Is it Classic or Superserver? What
platforms are the server and the gbak client running on? There are a couple
of fairly obscure bugs (fixed in the forthcoming Fb 1.5.3 release) that
might be behind this, if we knew something about the structure of the table
where the bad data was encountered.
./heLen
>Hi all,The client can't communicate with the host any more.
>
>Whilst restoring a FB1.5 DB I get the following errors,
>
>Can anyone tell me what the issue is and how to fix it.
>
>gbak: restoring data for table BUS_VEN
>gbak: adjusting an invalid decompression length from -52 to -11
>ERROR: Unable to complete network request to host "PC1".
>Error reading data from the connection.
>An existing connection was forcibly closed by the remote host.It was the host machine that caused the connection to break. If you can
eliminate the possibility that someone pulled out a plug, there's a
possibility the restore error cause the server to crash.
Can you make it happen again? and, if so, are you able to check whether
the Firebird server is still running after you see this message? It would
be useful to get closer to identifying what was happening when the invalid
decompression was detected.
Are you able to restore a metadata-only backup?
Which Fb 1.5 release are you running? Is it Classic or Superserver? What
platforms are the server and the gbak client running on? There are a couple
of fairly obscure bugs (fixed in the forthcoming Fb 1.5.3 release) that
might be behind this, if we knew something about the structure of the table
where the bad data was encountered.
./heLen