In our environment we replicate tables and we then expect the IDAA copy to be kept in sync with the DB2 table (within reason). If a table gets 'suspended' for whatever the reason, the data on that table begins to grow stale. Queries submitted against those accelerated tables will report on ever more out of date information. Wait For Replication returns normal indication even when replication is 'suspended'.
|Who would benefit from this IDEA?||All customers who use replication to maintain data consistency.|
How should it work?
We think that the behavior may need to differ based on 'suspended' vs 'disabled' replication. If the table replication is 'suspended' we do not think that the Wait For Replication should indicate that all is normal.
|Customer Name||Principal Financial Group|