Event Level Sensors (DB_TRIG and DB_MON)

[Legacy User]

Anyone familiar with using these 2 WOBTRIG's?

What is the difference between the 2?

What other considerations are necessary for this to become functional.

[Anon Anon]

A DB_TRIG sits in the database itself, reacts when the trigger event occurs and notifies the WA manager. A DB_MON runs on a polling basis from the WA Manager, where it will go and check to see if the monitor action has occurred periodically, governed bythe agentparm parameter[b] db.trig.polling/interval.ms in milliseconds (default 10 seconds).

DB_TRIGs are more predictable as they only do something when the event occurs, but in the past i have found at customers that the DBAs need a bit of persuading to let us use it.

A DB_MON is less intrusive so DBAs are happy with it, but you can miss events. Example: if you are monitoring for an increase of 10 rows in a table, and the 10 rows are added then another 10 deleted within the monitor interval, the DB_MON can miss it.

[Nicolas Colicchio]

Unfortunately, I have not had to opertunity to have used a DB_Trig job ... however I have used the DB_MON.
As for the DB_Mon ... what is happenning is that the agent generates a SQL_Query that performs a count and monitors the results. Hence the Monitor will only fire when there is a increase or a decrease in the number of rows (depending on what you have coded). I had this confirmed way back by Cybermation. If I understand the DB_Trig correctly this a little more flexible in choosing the condition that fires the WOB as it can monitor for updates as well. If my memory is correct the DB_Trig actually creates a databaser trigger process in DB2 ... where the the DB_MON is a SQL statement being issued by the agent repeatedly over and over until the condition is met.

hope this helps.

[Legacy User]

I know this is a old thread, but i have one more dumb question.  Are these WOBTRIG's just for distributed systems?  I was under the impression that these could be used for MainFrame DB2 workload, but it looks like to me it just for UNIX, WINDOWS, and the like.

[Anon Anon]

Database Monitor and Database Trigger Events

You can continuously trigger workload based on database activity using Database Monitor or Database Trigger Events.

Note: To use Database Monitor and Trigger Events, your system requires CA WA Agent for UNIX, Linux, or Windows and CA WA Agent for Databases.

A Database Monitor Event can monitor a database table for an increase or decrease in the number of rows. To monitor the database for specific changes, you can add a monitor condition to the Event definition. Whenever the condition is met, the server runs the Application referenced in the Event.

Database Monitor Events count the number of rows that satisfy the monitor condition using a polling interval, which is every 10 seconds by default. Database Monitor Events do not detect other updates to a row or changes to the number of rows that cancel each other out during the polling interval. For example, suppose that within a 10-second interval, a row is added while another row is deleted. Since the total number of rows did not change, the Database Monitor Event does not detect the row addition and deletion.

A Database Trigger Event can monitor a database table for added rows, deleted rows, or updated rows. To monitor the database for specific changes, you can add a trigger condition to the Event definition. Whenever the condition is met, the server runs the Application referenced in the Event.

Each Database Trigger Event creates a database trigger on the database. The database trigger templates that the agent uses are located in the directory where the agent is installed. The template files are named dbtrig

DB_type_name.properties, for example, dbtrigOracle.properties. Contact your database administrator before choosing to use a Database Trigger Event.

Note: A table that is being monitored should not be dropped. The Database Monitor or Database Trigger Event will remain active, even though the table has been dropped.

 

HTH

Allen Thennes

 

[Legacy User]

I want to know, do these Event Level Sensors work with Z/OS Mainframe DB2 tables, if so, how do they communicate?  Via the CA WA Agent for Databases? Where does that run or where is that defined? UNIX?  Is that a separate product purchase?  These are databases that are on the mainframe (z/os only).Not distributed..

[Lucy Zhang]

You can install the CA WA Agent for Databases on distributed platform (windows or unix) which can connect to the mainframe DB2. Currently there is no direct connection between ESP and mainframe DB2 without agent.