Hi,
I have recently started using nbackup and have a system where, at the
end of an attempt to do a level 0 I got
Fatal lock manager error: invalid lock id (158048), errno: 22
--Invalid argument
attempts to do subsequent level 1 backups produced:
unsuccessful metadata update
-Database is alrea
Hello Nick,
It seems like you have database corruption.
What is Firebird version?
Regards,
Alexey Kovyazin
IBSurgeon (www.ib-aid.com)
> Hi,
>
> I have recently started using nbackup and have a system where, at the
> end of an attempt to do a level 0 I got
>
> Fatal lock manager error: invalid l
sorry, didn't think to say, its version 2.1.4
On 31 October 2011 17:21, Alexey Kovyazin wrote:
> **
>
>
> Hello Nick,
>
> It seems like you have database corruption.
> What is Firebird version?
>
> Regards,
> Alexey Kovyazin
> IBSurgeon (www.ib-aid.com)
>
>
> > Hi,
> >
> > I have recently starte
the level 0 backup restores ok and gbak will then backup & restore that,
could the corruption be somewhere that that doesn't matter?
how can I find and deal with it?
On 1 November 2011 09:47, Nick Upson wrote:
> sorry, didn't think to say, its version 2.1.4
>
>
> On 31 October 2011 17:21, Alexey
Hello,
Unfortunately, I can't say more without thorough investigation.
It can be bug or corruption or misconfiguration.
Regards,
Alexey Kovyazin
> the level 0 backup restores ok and gbak will then backup& restore that,
> could the corruption be somewhere that that doesn't matter?
> how can I fi
Hi,
I've just had 2 level 2 backups, 5 mins apart, the first was ok, the second
wasn't, outputting
Fatal lock manager error: invalid lock id (43240), errno: 22
--Invalid argument
subsequent calls to nbackup (all levels including 0) result in
unsuccessful metadata update
-Database is already in
