peteh wrote:
> Hi Serge;
> That makes sense. Given the monitor switch settings below, would we
> incur any significant overhead by turning the "LOCK" switch on? Seems
> like if the Statement and Timestamp switches are already on, the impact
> would be minimal. Can you (or the the "backstage") confirm? Thanks very
> much!
>
> Pete H
>
> ---------------------------------------------------------------
> Default database monitor switches
> Buffer pool (DFT_MON_BUFPOOL) = ON
> Lock (DFT_MON_LOCK) = OFF
> Sort (DFT_MON_SORT) = ON
> Statement (DFT_MON_STMT) = ON
> 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
> ----------------------------------------------------------------
>
Backstage says impact of the monitor switch should be below 4% (erring
on the save side). I'm told that the LOCK snapshot itself will hit
though unlike the other snapshots. You will see a blip when it's taken.

Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab