As of today, Insync latency is reported via "Q8STCRL: The current replication latency for this DB2 system". This provides an overall latency but does not help which table is the most contributer to the latency. If customers monitor a high latency in replication, they would like to see the details in table level
|Who would benefit from this IDEA?||all IDAA Users who use Incremental Update|
How should it work?
If this table level detail is externalized and provided via DISPLAY ACCEL command with additional fields, or written to db2 tables for external access and monitoring, that would be useful. When there is a high latency, all customers want to know which table is causing this high latency (if the latency is because of high number of changes)
|Customer Name||RBC, Canada|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions