Yeah, -v gives additional 'total' of all memories used.
So for the case of:
Monh other fcmbp
16.0K 7.4M 4.3M
'db2mtrk -i -v' returns all the above in bytes plus the total
(16K+7.4M +4.3m) in bytes.
What baffles me is that given the same condition (3 connections to
TOOLSDB), why does db2mtrk show a significantly different 'map' after
db2 instance is restarted? Likewise for memory usage by db2syscs.exe
in task mgr?
Thanks..
"Fan Ruo Xin" <fa*****@sbcglobal.net> wrote in message news:<08****************@newssvr26.news.prodigy.co m>...
(1). Use db2mtrk -i -v will give you more words, such as applctlh will be
application control heap ...
When using option -v, which also show you the total memory for the
instance part, db part, agent part ...
(2). On Windows platform, db2 use multiple threads. That is why you found
db2sysc almost hold up all the memory.
(3). db2stop/db2start did not startup the database, only the memory used by
db2 server part.
"nek" <ne*****@hotmail.com> wrote in message
news:1a**************************@posting.google.c om... Would someone care to comment the following results of DB2MTRK execution,
thanks.
The platform is W2K SP with DB2 V8.1, SP2.
We have this result when running db2mtrk -i
Appctlh utilh pckcacheh catcacheh bph bph bph
96.0K 16.0K 3.4M 320.0K 1.0G 592.0K 336.0K
bph bph lockh dbh appctlh appctlh appctlh
208.0K 144.0K 39.7M 7.9M 16.0K 16.0K 16.0K
Appctlh utilh pckcacheh catcacheh bph bph bph
624.0K 16.0K 320.4K 160.0K 7.9M 1.1M 592.0K
bph bph bph lockh dbh Monh other
336.0K 208.0K 144.0K 256.0K 1.1M 336.0K 89.6M
fcmbp
4.3M
From task manager, db2syscs shows it uses up (approx.) 1.2 GB of memory.
After db2stop/start:
db2mtrk shows:
Monh other fcmbp
16.0K 7.4M 4.3M
And db2syscs uses about 23,980K of memory.
There are only THREE connections from TOOLSDB before and after running
db2mtrk.
Why is the discrepancy of memory usage so HUGE after db2stop/start?
