This is a companion question to "how long has a transaction been running?"

I have not encountered a blocking checkpoint indication in an onstat header in many years.  If I run an onstat command every second in a script, piping to grep, what the header line look like so that I can use it as a jump-off point to start looking into transactions and sessions.  (And hopefully only from other onstat command, avoiding the sysmaster database.)

There!  I did say it would be simpler! ;-)

Thanks much, all.

I would just do a case-insensitive grep for "block" from the "onstat -".  Here's a few examples of blocking:

IBM Informix Dynamic Server Version 12.10.FC10XKAEE -- On-Line (CKPT REQ) -- Up 16 days 00:54:04 -- 168145444 Kbytes
Blocked:CKPT

IBM Informix Dynamic Server Version 12.10.FC10XKAEE -- On-Line (CKPT INP) -- Up 1 days 20:05:18 -- 168145444 Kbytes
Blocked:ARCHIVE_EBR

IBM Informix Dynamic Server Version 11.70.FC7 -- On-Line (LONGTX) -- Up 10 days 20:15:50 -- 831840 Kbytes

Blocked:LONGTX

I wouldn't get too tied into the format, but if you have "blocked" anywhere in that it's probably of interest.

I don't recommend running this every second as you might generate too many false positives.  You could for example poll every 30 seconds and if you find a block, then poll every 5 seconds to see if it goes away.  If it hasn't gone away in 30 seconds, then maybe raise an alert.

I found this link which lists the different types of blocks:  Monitor the database server status - IBM Documentation

This is a companion question to "how long has a transaction been running?"

I have not encountered a blocking checkpoint indication in an onstat header in many years.  If I run an onstat command every second in a script, piping to grep, what the header line look like so that I can use it as a jump-off point to start looking into transactions and sessions.  (And hopefully only from other onstat command, avoiding the sysmaster database.)

There!  I did say it would be simpler! ;-)

Thanks much, all.