Hi All,
One of our Test Databases (DB2 UDB 9.5 FP4 on AIX) has been consistently crashing. On analysing the db2diag.log the following warning message is displayed:-

ADM4000W A catalog cache overflow condition has occurred. There is no error
but this indicates that the catalog cache has exceeded the configured maximum
size. If this condition persists, you may want to adjust the CATALOGCACHE_SZ
DB configuration parameter.

2009-09-30-07.49.06.691908 Instance:vproto Node:000
PID:2318496(db2agent (instance) 0) TID:7335 Appid:*LOCAL.vproto.090930054857
oper system services sqloEDUCodeTrapHandler Probe:999

ADM14001C An unexpected and critical error has occurred: "Trap". The instance
may have been shutdown as a result. "Automatic" FODC (First Occurrence Data
Capture) has been invoked and diagnostic information has been recorded in
directory

The parameter CATALOGCACHE_SZ is set to Automatic and we have tried to alter it's value but it did not work.
On analyzing the trap files that were generated it was discovered that some "Segementation Violation" was causing these repeated crashes.

Me and my team are have run out of ideas, please help!!!

Do you have STMM turned on?

Andy

Is ADM4000W logged right before the crash and by the same db2agent? The crash may not be related to this warning. You need to look at the trap file created in the FODC dir in order to determine why it's crashing. I'd suggest to open a pmr to address the crash.

Hi,
Thanks for the replies.
@ANDY: I am sorry but I don't know what STMM is? Can you please elaborate?
@db2girl: We have opened a PMR but I was trying to find out if someone has faced such a senario before.

Regards
Ashwin

STMM is Self Tunning Memory Manager its on V 9 onwards
whts is version and db2level 32bit or 64bit
regds
Paul

Guys,
We have similar problem with DB2V9.5 FP4 on Win2k3
even after 2 months IBM software support (PMR) could not find root cause.
They only know that some memory corruption occurs.

We are sure that in our case TOOLSDB's auto-maint feature was causing problems.
Now you might have TOOLSDB in different instance. If you are having TOOLSDB in same instance, try turning all Auto Maint features to off.

Regards,
DBFinder

Hi Friends,
Thanks for the replies.
@Paul: We do have STMM turned on. We are working on db2 9.5 FP 4 (64 bit instance)
We thought we had got a solution by removing the DB2MEMMAXFREE instance variable, but the problem started again after a day.

Regards
Ashwin