Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Solaris 2.6
Informix 7.31UC4
What causes this? Especially as my locks have just been increased from 200000 to
550000?
ISAM error: Lock Timeout Expired
↪ replying to Geezer From The Freezer
Art S. Kagel — — source: Usenet: comp.databases.informix
On Thu, 24 Jun 2004 10:03:45 -0400, Geezer From The Freezer wrote:
> Solaris 2.6
> Informix 7.31UC4
>
> What causes this? Especially as my locks have just been increased from
> 200000 to 550000?
>
> ISAM error: Lock Timeout Expired
This task has SET LOCK MODE TO WAIT <some # seconds>; set and was waiting on
a lock that was not released in time. Looks like some other app was badly
designed to hold locks for long periods of time. Look for interactive apps
that fetch a row for update and present it to a user for modification while
holding the lock. If the user goes to lunch or just gets a phone call ...
WHAM ... other apps/users are getting lock timeout errors.
Art S. Kagel
↪ replying to Geezer From The Freezer
Neil Truby — — source: Usenet: comp.databases.informix
"Geezer From The Freezer" <Geezer@Freezer.com> wrote in message
news:40DADF41.86D12603@Freezer.com...
> Solaris 2.6
> Informix 7.31UC4
>
> What causes this? Especially as my locks have just been increased from
200000 to
> 550000?
>
> ISAM error: Lock Timeout Expired
Bad application design.
User B is waiting for a row locked by user A, but cannot obtain it in the
requisite time, typically 5 minutes.
The total number of locks available does not affect this situation.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.