Hi Ann,

I am running with a standard configuration, and the time period between
such problems is averaging a month so a debug version on this database
system, would not be practical.

So, perhaps it is an issue with lock parametres. What setting would you
recommend for a database that has about 150 concurrent connections at
any one time with a average database size of 30 GB? The number of
tables, procedures and views is also on the order of about a thousand
objects or more......

I would like to think that it is a misconfigured server on my part vs a
problem with the lock manager itself.

best regards

Dalton

Ann W. Harrison wrote:

>
> 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
>
>