Hi Dalton,


My guess is that the problem is in the lock manager, not gbak
since gbak is just another layered application. An invalid lock
id is probably a symptom of a memory corruption, but that's just
a guess. Would it be possible for you to run a debugging version
of the server and capture a dump at the time the error occurs?

The other question that occurs to me is whether you've changed the
lock parameters... this could (possibly) be an unfortunate symptom
of running out of lock space, or on the other hand, it could be
an unfortunate side-effect of having increased the size of the
lock table beyond the limits we test...


Regards,


Ann