Running db2 8.1 on aix 5.1.

We are testing some Quest database tools and have run into a situation
where we keep getting the following error message when trying to use
the SQL analysis tool.

D(70032); SQC70012E - DB2 statement START EVENT MONITOR failed in
UdbExecDirect operation at location: Dispatcher 2965. Reason: [IBM][CLI
Driver][DB2/6000] SQL0973N Not enough storage is available in the
"MON_HEAP_SZ" heap to process the statement. SQLSTATE=57011 .

We have tripled our MON_HEAP_SZ to 512 but still get the error.

In investigating we were surprised to see that ALL the dbm event
monitors were turned on.

Switch list for db partition number 0
Buffer Pool Activity Information (BUFFERPOOL) = ON 09-27-2005
06:00:10.033814
Lock Information (LOCK) = ON 09-27-2005
00:14:19.631281
Sorting Information (SORT) = ON 09-27-2005
06:00:10.033817
SQL Statement Information (STATEMENT) = ON 09-27-2005
06:00:10.033810
Table Activity Information (TABLE) = ON 09-27-2005
06:00:10.033812
Take Timestamp Information (TIMESTAMP) = ON 09-19-2005
05:19:47.053604
Unit of Work Information (UOW) = ON 09-27-2005
06:00:10.033807

Most of these seem to be turning on around 6AM which is when Quest is
started.

The default settings in the dbm cfg are all off

Default database monitor switches
Buffer pool (DFT_MON_BUFPOOL) = OFF
Lock (DFT_MON_LOCK) = OFF
Sort (DFT_MON_SORT) = OFF
Statement (DFT_MON_STMT) = OFF
Table (DFT_MON_TABLE) = OFF
Timestamp (DFT_MON_TIMESTAMP) = ON
Unit of work (DFT_MON_UOW) = OFF
Monitor health of instance and databases (HEALTH_MON) = OFF

and the database level monitor switches are as follows:

Monitor Recording Switches

Switch list for db partition number 0
Buffer Pool Activity Information (BUFFERPOOL) = OFF
Lock Information (LOCK) = OFF
Sorting Information (SORT) = OFF
SQL Statement Information (STATEMENT) = OFF
Table Activity Information (TABLE) = OFF
Take Timestamp Information (TIMESTAMP) = ON 09-19-2005
05:19:47.053604
Unit of Work Information (UOW) = OFF


I don't see a way to turn these dbm event monitors off and assume that
the monitoring tool must be involved in that. Is that correct?

Thanks in advance.

Well, the stuff you see in the DFT_MON_* really has nothing to do with
event monitors. To see what event monitors you have defined in your
database, connect to it and check out the syscat.eventmonitors view.

Quest probably is the one turning on your montior switches. Otherwise
it wouldn't be able to present you with much in the way of monitor
data... as I recall, there's a dialog that comes up when you start QC
that asks you what monitor elements you're interested in.

But, as I said, EVENT MONITORS are different beasts altogether. Check
out the CREATE EVENT MONITOR statement, or the monitor guide and
reference, for more information.

/T

Got it thanks