--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

EVMONNAME                      STATE       VERSIONNUMBER TARGET_TYPE------------------------------ ----------- ------------- -----------LOCKEVMON                                0      10050500 UTRACE_EVMON                              0      10050500 T​

I understand, that you have consolidated the 4 event-monitors pre-reqs in a single script..  That's fine.
(Maybe the statistics one should be separate script, which is the only one that really demmands changes in WLM statistics collection to be done.. So,  if one particular user does not checks to use this,  but wants only to enables the other 3,  it will be prompted to make WLM changes, where this is really not necessary., but this is another subject... )  

 Problem is that,  when I try to see lock and utility history in DMC,  I am still prompted with the warning message that the pre-reqs are not met and need to review the script. 

But I have done everything  that I believe should be necessary,  I have created the special bufferpool, created the monitor tablespace, and also created the systemp space..   I just did not execute the statements that enables WLM statistics collection. 

Follow the details about the bps and tbspaces pre-reqs created on target db: 

BUFFERPOOLID BPNAME                NPAGES      PAGESIZE------------ --------------------  ----------- -----------           1 IBMDEFAULTBP                   -2        4096           2 BPNB04K                        -2        4096           3 BPNB08K                        -2        8192           4 BPEVMON32K                   1000       32768           5 BPNB32K                        -2       32768           6 BPBK2404KTINT                  -2        4096           7 CONSOLEPOOL                    -2       32768DATABASE PARTITION GROUP  PMAP_ID DATABASE PARTITION NUMBER    IN_USE------------------------- ------- ---------------------------- ------CONSOLEGROUP                    3                            0 YIBMCATGROUP                     0                            0 YIBMDEFAULTGROUP                 1                            0 YTBSPACE              TBSPACEID   PAGESIZE    TBSPACETYPE DATATYPE DBPGNAME             BUFFERPOOLID-------------------- ----------- ----------- ----------- -------- -------------------- ------------TSST32K0001                  185       32768 S           T        IBMTEMPGROUP                    4TS4MONITOR                   286       32768 D           L        CONSOLEGROUP                    7​

What else is missing ? 

Regards

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

EVMONNAME                      STATE       VERSIONNUMBER TARGET_TYPE------------------------------ ----------- ------------- -----------LOCKEVMON                                0      10050500 UTRACE_EVMON                              0      10050500 T​

I understand, that you have consolidated the 4 event-monitors pre-reqs in a single script..  That's fine.
(Maybe the statistics one should be separate script, which is the only one that really demmands changes in WLM statistics collection to be done.. So,  if one particular user does not checks to use this,  but wants only to enables the other 3,  it will be prompted to make WLM changes, where this is really not necessary., but this is another subject... )  

 Problem is that,  when I try to see lock and utility history in DMC,  I am still prompted with the warning message that the pre-reqs are not met and need to review the script. 

But I have done everything  that I believe should be necessary,  I have created the special bufferpool, created the monitor tablespace, and also created the systemp space..   I just did not execute the statements that enables WLM statistics collection. 

Follow the details about the bps and tbspaces pre-reqs created on target db: 

BUFFERPOOLID BPNAME                NPAGES      PAGESIZE------------ --------------------  ----------- -----------           1 IBMDEFAULTBP                   -2        4096           2 BPNB04K                        -2        4096           3 BPNB08K                        -2        8192           4 BPEVMON32K                   1000       32768           5 BPNB32K                        -2       32768           6 BPBK2404KTINT                  -2        4096           7 CONSOLEPOOL                    -2       32768DATABASE PARTITION GROUP  PMAP_ID DATABASE PARTITION NUMBER    IN_USE------------------------- ------- ---------------------------- ------CONSOLEGROUP                    3                            0 YIBMCATGROUP                     0                            0 YIBMDEFAULTGROUP                 1                            0 YTBSPACE              TBSPACEID   PAGESIZE    TBSPACETYPE DATATYPE DBPGNAME             BUFFERPOOLID-------------------- ----------- ----------- ----------- -------- -------------------- ------------TSST32K0001                  185       32768 S           T        IBMTEMPGROUP                    4TS4MONITOR                   286       32768 D           L        CONSOLEGROUP                    7​

What else is missing ? 

Regards

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

EVMONNAME                      STATE       VERSIONNUMBER TARGET_TYPE------------------------------ ----------- ------------- -----------LOCKEVMON                                0      10050500 UTRACE_EVMON                              0      10050500 T​

I understand, that you have consolidated the 4 event-monitors pre-reqs in a single script..  That's fine.
(Maybe the statistics one should be separate script, which is the only one that really demmands changes in WLM statistics collection to be done.. So,  if one particular user does not checks to use this,  but wants only to enables the other 3,  it will be prompted to make WLM changes, where this is really not necessary., but this is another subject... )  

 Problem is that,  when I try to see lock and utility history in DMC,  I am still prompted with the warning message that the pre-reqs are not met and need to review the script. 

But I have done everything  that I believe should be necessary,  I have created the special bufferpool, created the monitor tablespace, and also created the systemp space..   I just did not execute the statements that enables WLM statistics collection. 

Follow the details about the bps and tbspaces pre-reqs created on target db: 

BUFFERPOOLID BPNAME                NPAGES      PAGESIZE------------ --------------------  ----------- -----------           1 IBMDEFAULTBP                   -2        4096           2 BPNB04K                        -2        4096           3 BPNB08K                        -2        8192           4 BPEVMON32K                   1000       32768           5 BPNB32K                        -2       32768           6 BPBK2404KTINT                  -2        4096           7 CONSOLEPOOL                    -2       32768DATABASE PARTITION GROUP  PMAP_ID DATABASE PARTITION NUMBER    IN_USE------------------------- ------- ---------------------------- ------CONSOLEGROUP                    3                            0 YIBMCATGROUP                     0                            0 YIBMDEFAULTGROUP                 1                            0 YTBSPACE              TBSPACEID   PAGESIZE    TBSPACETYPE DATATYPE DBPGNAME             BUFFERPOOLID-------------------- ----------- ----------- ----------- -------- -------------------- ------------TSST32K0001                  185       32768 S           T        IBMTEMPGROUP                    4TS4MONITOR                   286       32768 D           L        CONSOLEGROUP                    7​

What else is missing ? 

Regards

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

EVMONNAME                      STATE       VERSIONNUMBER TARGET_TYPE------------------------------ ----------- ------------- -----------LOCKEVMON                                0      10050500 UTRACE_EVMON                              0      10050500 T​

I understand, that you have consolidated the 4 event-monitors pre-reqs in a single script..  That's fine.
(Maybe the statistics one should be separate script, which is the only one that really demmands changes in WLM statistics collection to be done.. So,  if one particular user does not checks to use this,  but wants only to enables the other 3,  it will be prompted to make WLM changes, where this is really not necessary., but this is another subject... )  

 Problem is that,  when I try to see lock and utility history in DMC,  I am still prompted with the warning message that the pre-reqs are not met and need to review the script. 

But I have done everything  that I believe should be necessary,  I have created the special bufferpool, created the monitor tablespace, and also created the systemp space..   I just did not execute the statements that enables WLM statistics collection. 

Follow the details about the bps and tbspaces pre-reqs created on target db: 

BUFFERPOOLID BPNAME                NPAGES      PAGESIZE------------ --------------------  ----------- -----------           1 IBMDEFAULTBP                   -2        4096           2 BPNB04K                        -2        4096           3 BPNB08K                        -2        8192           4 BPEVMON32K                   1000       32768           5 BPNB32K                        -2       32768           6 BPBK2404KTINT                  -2        4096           7 CONSOLEPOOL                    -2       32768DATABASE PARTITION GROUP  PMAP_ID DATABASE PARTITION NUMBER    IN_USE------------------------- ------- ---------------------------- ------CONSOLEGROUP                    3                            0 YIBMCATGROUP                     0                            0 YIBMDEFAULTGROUP                 1                            0 YTBSPACE              TBSPACEID   PAGESIZE    TBSPACETYPE DATATYPE DBPGNAME             BUFFERPOOLID-------------------- ----------- ----------- ----------- -------- -------------------- ------------TSST32K0001                  185       32768 S           T        IBMTEMPGROUP                    4TS4MONITOR                   286       32768 D           L        CONSOLEGROUP                    7​

What else is missing ? 

Regards

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

• One known reason is DB connection timeout. When console is trying to get db connection to validate the event monitor prerequisites, it timeout in 1 mintues, then returned validation failure to frontend. Frontend still reports the prerequisites validation failure.
• Another known reason is the db connection's authorization issue. It's better to using "db2inst1" in connection profile to enable data collection. Some other user id may not have the required privilege to perform the operation.

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

• One known reason is DB connection timeout. When console is trying to get db connection to validate the event monitor prerequisites, it timeout in 1 mintues, then returned validation failure to frontend. Frontend still reports the prerequisites validation failure.
• Another known reason is the db connection's authorization issue. It's better to using "db2inst1" in connection profile to enable data collection. Some other user id may not have the required privilege to perform the operation.

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

• One known reason is DB connection timeout. When console is trying to get db connection to validate the event monitor prerequisites, it timeout in 1 mintues, then returned validation failure to frontend. Frontend still reports the prerequisites validation failure.
• Another known reason is the db connection's authorization issue. It's better to using "db2inst1" in connection profile to enable data collection. Some other user id may not have the required privilege to perform the operation.

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​

Hi @xiao mingguang

Now we are talking...

Thanks for the log information...  I am using windows, and the path location are bit different.
​On windows the logs are located at 'Install-path\resources\bin\logs' sub dir.  

So,  I kept eye on monitor.0 log , and deactivated the event monitor in the profile, as you suggested, and enabled it back to force their creation. 

It was really lack of privileges... 

Initially lack of SYSMON authority. 

### Error querying database.  Cause: com.ibm.db2.jcc.am.SqlException: The requested command or operation failed because the user ID does not have the authority to perform the requested command or operation.  User ID: "DSMUSR1".. SQLCODE=-1092, SQLSTATE=     , DRIVER=4.26.14### The error may exist in com/ibm/aps/tools/monitor/collector/mybatis/mapper/EventMonitorLockingMapper.xml### The error may involve com.ibm.aps.tools.monitor.collector.mybatis.mapper.EventMonitorLockingMapper.queryFixedSize-Inline### The error occurred while setting parameters### SQL: select tbsp_type,tbsp_auto_resize_enabled,tbsp_max_size  from sysibmadm.tbsp_utilization where tbsp_name = 'TS4MONITOR'### Cause: com.ibm.db2.jcc.am.SqlException: The requested command or operation failed because the user ID does not have the authority to perform the requested command or operation.  User ID: "DSMUSR1".. SQLCODE=-1092, SQLSTATE=     , DRIVER=4.26.14

This one was solved by granting SYSMON to the DMC-user-id monitoring this db. 

Then, in the next monitor cycle..  another error, due lack of privileges: 

monitor (197)   NOXGR   db2admin        Dec 15, 2019 1:19:46 PM [16edb6a761436633dda7294edd322398]      ERROR    Mymon MonitorCollectorRunnable::run:  Event monitor EventMonitorLocking failed to create.org.apache.ibatis.exceptions.PersistenceException:### Error updating database.  Cause: com.ibm.db2.jcc.am.SqlSyntaxErrorException: The statement failed because the authorization ID does not have the required authorization or privilege to perform the operation.  Authorization ID: "DSMUSR1".  Operation: "CREATE EVENT MONITOR". Object: "TS4MONITOR".. SQLCODE=-551, SQLSTATE=42501, DRIVER=4.26.14### The error may involve com.ibm.aps.tools.monitor.collector.mybatis.mapper.EventMonitorLockingMapper.createEvmon-Inline### The error occurred while setting parameters### SQL: create event monitor RTMON_EVMON_LOCKING for locking write to table   LOCK (table ibm_rtmon.lock_event    in TS4MONITOR    ),   LOCK_PARTICIPANTS (table ibm_rtmon.lock_participants    in TS4MONITOR    ),   LOCK_PARTICIPANT_ACTIVITIES (table ibm_rtmon.lock_participant_activities    in TS4MONITOR    ) manualstart### Cause: com.ibm.db2.jcc.am.SqlSyntaxErrorException: The statement failed because the authorization ID does not have the required authorization or privilege to perform the operation.  Authorization ID: "DSMUSR1".  Operation: "CREATE EVENT MONITOR". Object: "TS4MONITOR".. SQLCODE=-551, SQLSTATE=42501, DRIVER=4.26.14

This one, was solved by granting 'USE' privilege in the target tablesapce TS4MONITOR. 

db2 "grant use of tablespace TS4MONITOR TO USER DSMUSR1"

Please,  we need these privileges/authorities required to be documented..   Not only these,  but ALL privileges and authorities required by the DSM monitor user in the target dbs..  And we need to be specific here..   not asking excessive privileges like SYSADM or DBADM authority which grants excessive power to DMC monitoring users. 

After these two missing privileges were granted..  I could see the event monitor got created in the target db. 

Regards

------------------------------
Samuel Pizarro

Original Message:
Sent: Wed December 11, 2019 11:28 PM
From: XIAO MIN ZHAO
Subject: Locking and Utility Monitoring requiring WLM ? why ?

Hi @Samuel Pizarro​ ,  the log is recorded in files folder /ibm-datamgmtconsole/logs/monitor.*, monitor.0 includes the latest log. And would you please share with me the API's output by insect Chrome browser's network, as following: Another workaround to bypass the problem is: Please try disable / enable event monitor options in monitor profile. These operation will trigger console to drop /create event monitors in the monitored Database immediately if all the prerequistes are meet.

• One known reason is DB connection timeout. When console is trying to get db connection to validate the event monitor prerequisites, it timeout in 1 mintues, then returned validation failure to frontend. Frontend still reports the prerequisites validation failure.
• Another known reason is the db connection's authorization issue. It's better to using "db2inst1" in connection profile to enable data collection. Some other user id may not have the required privilege to perform the operation.

--NOTICE: please check whether there is 32kb pagesize temporary tablespace firstly, if not please create a new one.--create a bufferpool with page size 32kbCREATE BUFFERPOOL CONSOLEPOOL ALL DBPARTITIONNUMS SIZE 1000 AUTOMATIC PAGESIZE 32768;--create a partition spannning all partitionsCREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;--create the 32kb tablespace with max size 2G specifiedCREATE 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 spaceSELECT 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 informationALTER WORKLOAD SYSDEFAULTUSERWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;ALTER WORKLOAD SYSDEFAULTADMWORKLOAD COLLECT AGGREGATE ACTIVITY DATA BASE;​