I seem to recall - a long time ago in the days when I did any of this,
that if you did not specify 'FOR READ ONLY' when you opened a cursor - it
always took out a write lock.

Lin



Internet
specially (AT) processed (DOT) almost.meat
Sent by: info-ingres-bounces (AT) kettleriver...ting (DOT) com
10/03/2011 12:45
Please respond to
info-ingres (AT) kettleriverconsulting (DOT) com


To
info-ingres (AT) kettleriverconsulting (DOT) com
cc

Subject
Re: [Info-Ingres] readlock=nolock but table is locked






Mark wrote:

I hope you fully understand ALL the implications of that.

That can't be right. In the first place if the application is using
READLOCK=NOLOCK it won't attempt a lock, won't wait, and won't time
out, so you won't see a lock timeout in the log. Furthermore if the lock
requests do timeout then then neither the application nor the server
is hanging. (The application might be looping and re-waiting though,
making it look like it's hanging.)

More likely an application bug. Use security query_text auditing or
trace point SC930 to see what the applications are doing.

Another possibility is that there is a third participant you don't know
about that is locking (taking an ordinary lock or a control lock).

--
Roy

UK Ingres User Association Conference 2011 will be on Tuesday June 7 2011.
Register at http://www.regonline.co.uk/ukiua2011


_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres


__________________________________________________ _________
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is prohibited.

Please refer to http://www.bnpparibas.co.uk/en/infor...de=ECAS-845C5H for additional disclosures.