DPA cannot currently monitor all aspects of a DB2 HADR standby instance with ROS (reads on standby) enabled.
DPA can currently monitor the basics of a DB2 instance database but not with any of the following DB2 DBM configuration monitor switches enabled:
| Unit of work | (DFT_MON_UOW) = OFF |
| Table | (DFT_MON_TABLE) = OFF |
| Statement | (DFT_MON_STMT) = OFF |
| Sort | (DFT_MON_SORT) = OFF |
| Lock | (DFT_MON_LOCK) = OFF |
| Buffer pool | (DFT_MON_BUFPOOL) = OFF |
The problem is DPA's polling issues calls to the DB2 instance that _possibly_ require a "writeable" database.
DB2 diagnostic log entry:
FUNCTION: DB2 UDB, buffer pool services, sqlbDirectWrite, probe:123
MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY
"The operation that attempted to modify the contents of the database failed"
DATA #1 : <preformatted>
Direct writes are not supported on HADR Standby database.
We have a need to monitor statement level performance on our standby server as we've shifted a bulk of our read-only workloads to the standby server. I understand if this is a no-go since the defect might well lie with IBM DB2 LUW HADR architecture.
