Thread: db2syscs.exe growth
03-14-11, 02:32 #1Registered User
- Join Date
- Feb 2009
Unanswered: db2syscs.exe growth
DB2 v9.7 fp 3a - Windows 2008 R2 only 16 GB Ram
One instance behind a WCM with 6 specific databases.
db2syscs.exe process grow to 7 GB even there is no real activity excepting some crontasks ? (is this normal?)
After some import activities (DB2 insert/update) it was reported to me later that no connections are possible !
First I found it responding very slow to commands like "list applications"and "db2stop" did not work and no connection was possible from the WCM different system.
The only solution was to manually kill db2syscs.exe. No error found in db2diag.log (and other relevant info)
In few seconds after restart db2syscs grow in size of 3 GB and then to 7 GB slower ... only those WCM crontasks were running
Snapshots for dynamic sql shows hundreds of select and several updates one of them:
UPDATE RELEASE.WPS_SCDTASK SET VERSION=? ,ROW_VERSION=?, TASKSUSPENDED=?, CANCELLED=?, NEXTFIRETIME=?, STARTBYINTERVAL=?, STARTBYTIME=?, VALIDFROMTIME=?, VALIDTOTIME=?, REPEATINTERVAL=?, MAXREPEATS=?, REPEATSLEFT=?, NAME=?, AUTOPURGE=?, FAILUREACTION=?, MAXATTEMPTS=?, QOS=?, PARTIT IONID=?, OWNERTOKEN=? WHERE (TASKID=? AND ROW_VERSION=?)
Here are some db parameters for the most important db reldb, jcrdb:
applheapsz 8192 stmtheap 32768 dbheap 3000 locklist 1000; logfilsiz 4000; logprimary 100; logsecond 20; logbufsz 256
After the implementation and imports are finished this db should be used extensively for query.
Can I try other things to avoid no connection situation again, diminish db2syscs size and improve performance or this configuration cannot do better?
Last edited by heartwork93; 03-14-11 at 02:35.
03-14-11, 02:53 #2:-)
Provided Answers: 1
- Join Date
- Jun 2003
- Toronto, Canada
I'm not sure why you are concerned about the DB2 instance using 7 GB if you have 16 GB of memory available (I'm assuming you run 64-bit DB2 on 64-bit Windows though).