I think they represent one and the same thing. :-) Keep in mind that the
catalog cache can grow into other areas of dbms shared memory...so if
the value being reported is higher than your mtrk stuff, it's because
your cache needed to grown beyond the max. Have a look at the db
snapshot values for the high water mark and number of cache overflows to
see if you might need to bump up the size of the cache.
hype wrote:
Hi,
could anyone explain the relationship between the "Catalog cache heap"
in the db2mtrk output and the database config parameter
catalogcache_sz.
Thanks,
Hype.