Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

OpenEdge Replication
OpenEdge 10.x

SYMPTOM(s):

promon shows different Activity counters for OpenEdge Replication source and target

FIX:

For example, promon on source shows -

Activity - Sampled at 12/05/07 14:59 for 0:00:02.

Event Total Per Sec Event Total Per Sec
Commits 2272 1136.0 Undos 0 0.0
Record Updates 2272 1136.0 Record Reads 0 0.0
Record Creates 2272 1136.0 Record Deletes 0 0.0
DB Writes 110 55.0 DB Reads 0 0.0
BI Writes 211 105.5 BI Reads 18 9.0
AI Writes 199 99.5

Promon for the target database covering the same (moreorless) period -

Activity - Sampled at 12/05/07 14:59 for 0:00:01.

Event Total Per Sec Event Total Per Sec
Commits 0 0.0 Undos 0 0.0
Record Updates 0 0.0 Record Reads 0 0.0
Record Creates 0 0.0 Record Deletes 0 0.0
DB Writes 53 53.0 DB Reads 0 0.0
BI Writes 98 98.0 BI Reads 9 9.0
AI Writes &nbs.p; 93 93.0

The difference in Commits, Record Updates and Creates between source and target is typical - source shows values for these, target never does.
This is expected behavior. There is a completely different code path for performing the operations specified by the ai log records than for doing the logical operations of normal forward processing. The counters are updated in the forward processing functions used for the /logical/ operations that generate the records that are written to the transaction log, not in the functions corresponding to the /physical/ operations specified by the log records.
That is, the replication agent updates the database based actions in individual notes, but the gathering of promon's record-level statistical data is performed at a much higher level where there is explicit knowledge of records.
dsrutil -C monitor agent will also show activity such as AI blocks being processed, while promon on the same target will show no values for Commits, Record Updates and Creates..