When a table with a XML column is replicated, we observed a high number of SMF Db2 accounting records, one for each row that a have a XML column.
The records are due to Db2 threads created by the replication process.
As the Db2 SMF records are going to the system logger this one has a fixed (hardcoded) threshold of 20% and gives alerts unneeded. It has also a bad impact on performance and does not respect the concept of Logical unit of work as it should be.
See TS002534012 42697,999,624
How should it work?
The replication process should not create on thread per Db2 row.
The replication process should do one thread according to the logical unit of work observed on the source side when the application is updating the source table.
|Priority Justification||We have a work around but not always applicable|
|Customer Name||Eurolcear SA/NV|