Hi:
This is a scenario of lock escalation. Escalation
happenes wheh MAXLOCKS is reached. Try increasing
MAXLOCKS and LOCKLIST accordingly in the DB cfg.
Make sure that wait time and deadlock check time is
not too long. Make it like 5 seconds (or) 5000 ms.
HTH
-- Vijay
--- Doug Carter <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I'm working on a new Java application that connects
> to a Linux DB2
> instance using JDBC. We're running a larger amount
> of data
> through it and are now seeing performance problems.
> The application
> status shows "UOW Waiting", but it's not clear what
> it's waiting on.
>
> The only interesting information I can find is in
> the db2diag.log
> file. It has lots of messages that look like this;
>
> ---
>
> 2001-08-31-09.59.09.743317 Instance:ops0001
> Node:000
> PID:24287(db2agent (OPS0001))
> Appid:*LOCAL.ops0001.010831165903
> data_management sqldEscalateLocks Probe:2
> Database:OPS0001
>
> -- Lock Count, Target : 1140, 570
> -- Table (ID) Name : (2;13) TR
> .USER_SESSION
> -- Locks, Request Type : 1124, X
> -- Result (0 = success): 0
>
> ---
>
> Does anyone know what this message means? Is it bad?
> Just info? Is
> this an indication of bad configuration setting or
> an ill-behaved app?
>
> TIA,
>
> Doug Carter
> WebCriteria
>
>
> =====
> To unsubscribe, send 'unsubscribe' to
> [EMAIL PROTECTED]
> For other info (and scripts), see
> http://people.mn.mediaone.net/scottrmcleod
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
