Why all the WLM events are recorded on the same node, even when the event tables are defined on multiple partitions?
ChunGao 270006J5PY Visits (4743)
Customer may find that WLM activity events may be recorded to one partition even with the event tables are defined on multiple partition.
WLM event collection depends on the "COLLECT ACTIVITY DATA" clause specified on the workload, service class, threshold or work action set. Data can be collected on the coordinating partition or all partitions. If apps are all connecting to the same partition, then all apps would have the same coordinator partition. Regardless whether the "COLLECT ACTIVITY DATA" clause is set to ON COORDINATOR DATABASE PARTITION or ON ALL DATABASE PARTITIONS, the events on coordinator node will be captured and written to table (assuming the target for data is a set of tables) on the coordinator node. In some environment this may cause a disk full situation. To prevent the disk full situation, you can set PCTDEACTIVATE clause to determine how many percentage of the tablespace can be used by the tables.
Or you may look into this option to use "SET CLIENT" to specify the CONN
so that you could use that to direct some users to different nodes.