The JCC LogMiner Loader handles unexpectedly large transactions.

One customer was successfully using the Loader until extensive maintenance revealed a performance issue. The company had been using the Loader to regularly process 4,000 transactions per second.  The DBAs did a convert/commit and changed the truncate table statements into delete from table. The result was transactions of half a million rows. Performance was no longer something to brag about.

Occasionally, contacting the support desk reveals something that exceeds the Loader's capacity. Some of these become enhancements to the product.

The next release of the Loader included an enhancement to adjust the locking approach automatically when a certain threshold was reached. The new approach avoided heavy use of the OpenVMS lock manager and achieved the goal of getting the huge transactions out of the way as quickly as possible so that regular processing could resume.