Catalog Cache Overflow

[Amy DBA]

Hi all, I'm not new to DB2, but I am new to Version 8. Does this mean I
should increase my CATALOGCACHE_SZ ? The old diag log messages used to
mention which specific parameter was causing problems, so that's why I'm not
sure.

Catalog Cache Overflow
total memory : 1067540
memory needed: 2580
current configured size: 1064960
current used size (OSS): 1064388
maximum used size (OSS): 1327104
entry type: 2

Amy

[Amy DBA]

I posted this over the weekend and I don't think anyone saw it. Does anyone
have any clue what this diag message means?

"Amy DBA" <te********@gmail.NOSPAM.com> wrote in message
news:4K****************@newssvr22.news.prodigy.com ...

Hi all, I'm not new to DB2, but I am new to Version 8. Does this mean I
should increase my CATALOGCACHE_SZ ? The old diag log messages used to
mention which specific parameter was causing problems, so that's why I'm not sure.

Catalog Cache Overflow
total memory : 1067540
memory needed: 2580
current configured size: 1064960
current used size (OSS): 1064388
maximum used size (OSS): 1327104
entry type: 2

Amy

[Serge Rielau]

DB2 has a (distributed) catalog cache.
Everytime you access a table, view or routine it will cache the relevant
information.
In a DPF system this offloads the catalog node and in general it
improves compile performance.
So in this case that cache filled up. What I don't know off hand is
whether DB2 just issued an LRU algorithm to make space or stole some
memory from another heap. (like the package heap).
Unless you see a performance problem when compiling queries I wouldn't
worry about it.

Cheers
Serge

[Pierre Saint-Jacques]

Amy, here's what I think:
current configured size:1064960+memory needed:2580=total memory: 1067540

DB2 caused the catalogue cache to "steal" the 2580 bytes from other
parms of the global shared memorry (either of:dbheap, package
cache,locklist,...).

maximum used size (OSS): 1327104 is the high water mark value reached
since the db was activated. This value should always be less than the
defined value in your db cfg. If not, you end up "stealing".

So yes, you should increase your catalogcache_sz to the value of the
high water mark, if:
You get that message often.

If this is a one-off occurence over a long monitoring time, I would not
bother all that much.

HTH, Pierre.
Amy DBA wrote:

I posted this over the weekend and I don't think anyone saw it. Does anyone
have any clue what this diag message means?

"Amy DBA" <te********@gmail.NOSPAM.com> wrote in message
news:4K****************@newssvr22.news.prodigy.com ...

Hi all, I'm not new to DB2, but I am new to Version 8. Does this mean I
should increase my CATALOGCACHE_SZ ? The old diag log messages used to
mention which specific parameter was causing problems, so that's why I'm

not

sure.

Catalog Cache Overflow
total memory : 1067540
memory needed: 2580
current configured size: 1064960
current used size (OSS): 1064388
maximum used size (OSS): 1327104
entry type: 2

Amy

--
Pierre Saint-Jacques - Reply to: sesconsjunk at attglobaljunk dot com
Reconstruct address: Remove the two junk and replace at and dot by
their symbols.
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.