When you issue "show post detail", you may see the output that may not have transactions and DMLs posted adding up to operations posted. Here is a sample output:
sp_ctrl (batch01:2300)> show post detail
Host : batch01
Source : o.KCFCSPLEX Queue : QPAC_KCFC
Operations
Target Status Posted Since Total Backlog
---------- --------------- ---------- ------------------ ---------- ----------
o.KCFCBAT Running 400995 11-May-07 10:24:17 130484 130387
Last operation posted:
Redo log: 13133 Log offset: 104099176
INSERT in "KCFC_USER"."ACLINKC" at 05/09/07 14:54:31
Post state : Commit transaction
Activation Id : 19
Current transaction Id : 2
ID of blocking transaction : 0
Number of open transactions : 0
Number of messages read released : 500
Operations posted : 100
Transactions posted : 5
Insert operations : 50
Update operations : 20
Delete operations : 15
Key cache hit count : 0
SQL cache hit count : 70 %
Here is the interpretation of the statistics:
You have total insert/delete/update = 85
But the transaction posted were only 2
The operations posted were 100
Here is the plausible explanation for what occurred:
The operations posted were 100 that comprised DMLs, DDLs, COMMIT/ROLLBACK as well as some internal or non-data messages.
The transaction posted were 5 that comprised COMMIT and/or ROLLBACK.
The total insert/delete/update were 85.
So as you can see, the operations posted will always be the highest out of these three as it is a superset and includes DML, DDL, commits and other type of messages which include internal and non-data messages (some Shareplex terminology). The transactions posted is a subset of the operations posted. It would generally be smaller than the total # of INSERTs, UPDATEs and DELETEs unless every DML is followed by a COMMIT, in which case it will be equal to the DMLs (INSERTs, UPDATEs and DELETEs) posted. The total DMLs posted (INSERTs, UPDATEs and DELETEs) is a subset of the total operations posted.
