Hello Xiao (sorry if this is not your first name),
thanks for looking into that.
The query returns the following:
| TBSP_TYPE |
TBSP_AUTO_RESIZE_ENABLED |
TBSP_MAX_SIZE |
| DMS |
1 |
2147483648 |
| DMS |
1 |
2147483648 |
| DMS |
1 |
2147483648 |
| DMS |
1 |
2147483648 |
| DMS |
1 |
2147483648 |
| DMS |
1 |
2147483648 |
| DMS |
1 |
2147483648 |
| DMS |
1 |
2147483648 |
Actually 1 row per partition as the tablespace was created in partition group CONSOLEGROUP which comprises all partitions:
CREATE DATABASE PARTITION GROUP CONSOLEGROUP ON ALL DBPARTITIONNUMS;
CREATE TABLESPACE TS4MONITOR IN CONSOLEGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 100M MAXSIZE 2G BUFFERPOOL CONSOLEPOOL;
Kind regards - Matthias
------------------------------
Matthias Gärtner-Schür
DBA
------------------------------
Original Message:
Sent: Mon January 13, 2020 04:03 AM
From: XIAO MIN ZHAO
Subject: Event Monitors and Monitor Tables not created by DMC
Hi Matthias,
From the error logs, the event monitors did not be created due to prerequisites validation failure. And the exact failure is: Console does not get expected results from the query:
select tbsp_type,tbsp_auto_resize_enabled,tbsp_max_size from sysibmadm.tbsp_utilization where tbsp_name = 'TS4MONITOR';
Would you please run this statement on your database, and show me the results? Then we can analysis further. Thanks!
------------------------------
XIAO MIN ZHAO
Original Message:
Sent: Fri January 10, 2020 07:11 AM
From: Matthias Gärtner-Schür
Subject: Event Monitors and Monitor Tables not created by DMC
Hello DMC Support Team,
I'm trying to activate DMC data collection for activity/utilities/locking/statistics which require creation of event monitors and tables on the target database. My database is a V10.5 DPF with 8 partitions.
After configuring the monitoring profile for this database and running the script for bufferpool/tablespace/temp tablespace/workload creation and alteration I don't get any event monitor data collected. I still get the message to run this preparation script.
- Recycling DMC does not help.
- The DSM_WORKLOAD has been successfully created in the target database, the default workloads have been successfully altered, but I do not see any event monitors registered in the DB2 catalog apart from the DB2DETAILDEADLOCK. This one should have been deactivated by DMC on creation of the new lock event monitor, (right?), but it is still active.
- According to Knowledgecenter documentation I should find a couple event monitor tables in schema IBM_RTMON, but DMC did not create any.
- I repeated the whole set-up procedure after removing the database from monitoring and setting back the objects in the target database to their original status. Still the same situation.
- I do not find any error messages in the db2diag.log
- DMC does not throw any error messages in the GUI apart from the reminder to run the config script for Responsiveness monitoring
- In the DMC monitor log I find the following message:
monitor (205) Jan 10, 2020 10:31:41 AM ERROR Mymon MonitorCollectorRunnable::run: Event monitor EventMonitorLocking failed to create. monitor (205) Jan 10, 2020 10:31:41 AM ERROR Mymon MonitorCollectorRunnable::run: Event monitor EventMonitorLocking failed to create. org.apache.ibatis.exceptions.TooManyResultsException: Expected one result (or null) to be returned by selectOne(), but found: 8
Maybe the tool has some issues with DPF (here 8 partitions)?
I'd like to ask you for help and guidance where to continue looking in order to identify the root cause for my issue.
I attached the monitor logs written after the restart of the DMC process. The database in question is CARD_T.
Many thanks in advance for looking into this matter.
Matthias
------------------------------
Matthias Gärtner-Schür
DBA
------------------------------
#Db2