Subject Re: gds_$receive failed error using gBak
Author Hernando Duque C
--- In firebird-support@yahoogroups.com, "Adam" <s3057043@...> wrote:
>
> --- In firebird-support@yahoogroups.com, "duque.hernando"
> <duque.hernando@> wrote:
> >
> > --- In firebird-support@yahoogroups.com, "Adam" <s3057043@> wrote:
> > >
> > > --- In firebird-support@yahoogroups.com, "duque.hernando"
> > > <duque.hernando@> wrote:
> > > >
> > > > Hi to all,
> > > >
> > > > I've a big trouble while making a backup with gBak (Firebird
1.5) I
> > > > get gds_$receive failed error. I've trying using gFix but no
> solution.
> > > >
> > > > I've searched the group posts looking for working arround tips for
> > > > this but no one of the solutions have worked yet.
> > > >
> > > > I've drop all indexes, constraints, primary keys and so on but no
> > > > solution.
> > > >
> > > > I'll appreciate for hints that let me find the object damaged
in the
> > > > database structure.
> > > >
> > >
> > > Try gbak with -v parameter. This might give you a pointer to the
> > > object that gbak is trying to backup at the time the failure
occurs.
> > > Also, try -g parameter to avoid performing garbage collection as
gbak
> > > runs. If there is corruption in a backversion only, this will
allow a
> > > backup to be made.
> > >
> > > Adam
> > >
> >
> > Hi, It seems that the corruption is not in a backversion because gbak
> > with -g parameter didn't work. The -v parameter shows that the
> > consistency check seems to be when writing one of the table's data. I
> > droped the table, but when running again gbak, the consistency check
> > moves to another table, when dropping it, then it moves to another...
> > and so on.
> >
>
> When you say it moves to another table, do you mean it moves to the
> next table, or that the next table was fine but a similar issue is
> encountered a couple of tables later?
>
> Are you able to perform a select * on the problematic tables?
>
> Adam
>

Adam, thank you for your post.

When I say it moves to another table, I mean it moves to the next
table and to the next and so on, with no tables being procesed ok any
further.

Im able to perform select * on the problematic tables but only if the
select returns one record using the primary key field.

Nando.