Hi Roberto,
If you want to collect event monitor data for some specified application, you can create a workload then contain application you wants, like this command:
CREATE WORKLOAD WORKLOAD_XXX APPLNAME ('xxx*','xxx*','xxx*','xxx*','xxx','xxx*');
then use alter workload command to collect related event monitor data you want, like this command:
ALTER WORKLOAD WORKLOAD_XXX COLLECT ACTIVITY DATA ON COORDINATOR WITH DETAILS;
if you don't want to collect event monitor data for some applications, you also create a workload and include these applications and the COLLECT ACTIVITY DATA option should not specified
I hope this answer can help you, thanks
------------------------------
HAI LEI SONG
------------------------------
Original Message:
Sent: Thu January 09, 2020 03:30 AM
From: Roberto Mandolini
Subject: For lock history do we need to setup work load manager ?
Hi all,
I'm just starting to move from DSM to new Console version ..
so, only one question by my side, how can be the impact on consumption and on the amount of data produced if you choose this option?
--Capture the statements for the default two workloads on the coordinator node. If you want to collect the activity data for all nodes of a multi-partition database, change the COORDINATOR option to ALL.
we have an heavy load on some servers
------------------------------
Roberto Mandolini
Original Message:
Sent: Wed January 08, 2020 12:42 PM
From: srijith sudhakaran
Subject: For lock history do we need to setup work load manager ?
to collect lock history do we need to setup work load manager ? do we need to run all the below statements provided in DMC message "Review and run theto make sure that your database satisfies all the prerequisites for event monitoring" ?
--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.
--create a bufferpool with page size 32kb
CREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;
--create a partition spannning all partitions
CREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;
--create the 32kb tablespace with max size 2G specified
CREATE TABLESPACE TS4MONITOR IN CONSOLEGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 100M MAXSIZE 2G BUFFERPOOL CONSOLEPOOL;
--check whether there is 32kb pagesize temporary table space
SELECT COUNT(1) FROM SYSCAT.TABLESPACES WHERE DATATYPE = 'T' AND PAGESIZE = 32768;
--Don't create TEMPSPACE2 if there is already a 32kb pagesize temporary tablespace. If no 32kb pagesize temporary tablespace, create a required one.
CREATE TEMPORARY TABLESPACE TEMPSPACE2 PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 4 BUFFERPOOL CONSOLEPOOL;
--Define a workload to filter the monitored console executed statements. Because the COLLECT ACTIVITY DATA option is not specified, the statement history will not collect the statements of the workload.
CREATE WORKLOAD DSM_WORKLOAD APPLNAME ('DSMAu*','DSMRt*','DS_ConnMgt*','DSSNAP*','DSMOQT','UC_*');
--Capture the statements for the default two workloads on the coordinator node. If you want to collect the activity data for all nodes of a multi-partition database, change the COORDINATOR option to ALL.
ALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT ACTIVITY DATA ON COORDINATOR WITH DETAILS;
ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT ACTIVITY DATA ON COORDINATOR WITH DETAILS;
--Capture the aggregate responsiveness workload information
ALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;
ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;
------------------------------
srijith sudhakaran
------------------------------
#Db2