more info, the last few lines of -v output from gbak are:

gbak: activating and creating deferred index FK_APABSE_LASTMODBYID
gbak: activating and creating deferred index FK_APBASE_CREATORID
gbak: activating and creating deferred index FK_TBLACTIVEPOWER_TBLELEMENT
gbak: activating and creating deferred index
FK_TBLACTIVEPOWER_TBLOUTSTATION
gbak: committing metadata
gbak:finishing, closing, and going home
Fatal lock manager error: invalid lock id (200168), errno: 22
--Invalid argument

On 31 August 2011 10:15, Nick Upson <nu@...> wrote:

> I have a script that does a backup and then attempts to create a database
> from that backup to verify it, on one system I have started sometimes
> getting the error message:
>
> Fatal lock manager error: invalid lock id (57768), errno: 22
> --Invalid argument
>
> I'm using 2.1.4 CS on linux (centos 5.4).
>
> Manually running the same command on the same backup works ok, so I figure
> it's some transient condition or combination of conditions, fortunately its
> a test system
> so I can run almost anything I want on it but where to start, I've just
> added the -v to the gbak command line and I'm going to make it take the
> backups more often to
> gain more evidence.
>
> --
> Nick Upson (01799 533252)
>
>


--
Nick Upson (01799 533252)


[Non-text portions of this message have been removed]