Just a guess - it looks like it may be a lock escalation failure; perhaps
you have exhausted LOCKLIST, and MAXLOCKS is at or near 100% ?
Try with an increased LOCKLIST and/or a reduced MAXLOCKS; or alter the query
to LOCK tablename IN EXCLUSIVE MODE.
Regards
Alex Levy
Sustainable Software Ltd.

-----Original Message-----
From: Kroon Hans
[mailto:db2udbdba-ezmlmshield-x14424416.[Email address protected]
Sent: 17 November 2006 14:43
To: LazyDBA Discussion
Subject: DB2 UDB 7.2.9 SQLstate 57011


DB2 UDB 7.2.9 SQLstate 57011


We got the following sqlstate from our application: SQLstate 57011
(Virtual storage or database resource is not available)

We don't have any problem with our db2 server (disk space is ok and also no
logfile problem) logprimary=5 and logsecond=15 and only 4 logfiles, but no
first active logfile.

db2diag.log:

2006-11-17-10.39.34.575000 Instance:X2B1_PRD Node:000
PID:249(db2syscs.exe) TID:455 Appid:C0A80106.1907.061117082717
data_management sqldEscalateLocks Probe:2 Database:MDI_X2B1
-- Lock Count, Target : 1252, 626
-- Table (ID) Name : (2;335) KLBBS .VERZAMELPRINT
-- Locks, Request Type : 1249

What is here the problem? We have tried to change the app_ctl_heap_sz but
this has no effect.

regards,
Hans Kroon


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



-----------------------------------------------
Scanned by 186k-NetCleanse, spam and virus protection



DB2 & UDB email list listserv db2-l LazyDBA home page