Ezequiel,
Set lock mode to wait will allow a thread to go to a wait state untilit can acquire a the lock it is requesting. This can be good and bad
depending on how long the thread has to wait. Unfortunately, Informix
has identified a bug with all IDS 7.2 and 7.3 where set lock mode to
wait does not work this way in a stored procedure. The thread will
wait on the first resource in a wait state and then the engine will
change the lock mode state to the default which is no wait. This is
causing us problems in which we are forced to redesign our application
because we cannot seem to get a bug fix for this.
Craig Lanford
Mailto:craiglanford@yahoo.com
---eglinsky@my-dejanews.com wrote:
>
> Sometimes, when I'm trying to execute a stored procedure, I'm
getting the
> following error message:
> -211 Cannot read system catalog catalog-table.
>
> After a while, seems like the row is un-locked and I can execute the
Stored
> Procedure properly.
>
> I heard something about the SET LOCK MODE TO WAIT method, what is it
good for?
> And what about the SYSPROCPLAN? How do I avoid the automatic
re-optimizing?
>
> Thank you very much for your help!
>
> Ezequiel Glinsky.
>
> -----== Posted via Deja News, The Leader in Internet Discussion
==-----
> http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member
Forum
>
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com