High CPU utilization may be observed when the Db2/z Log Capture is initially started on zOS either when the JOB that executes the Db2/z Capture is run or the Db2/z Capture Started Task is started. This occurs when many logs have to be read in order to resume Capture, when either the Job/Task was not executing for a long time or when it has been instructed to perform a Point-in-time recovery, requiring logs to be remined from some point in the past.
This may also occur due to support for Db2 Schema Evolution introduced in V4.0. If downstream Replicator Engines are not in use the --no-ddl-tracking option may be used to bypass the collection of schema information upon initiation of Capture.