While using db2top to monitor I sometimes see the DB2_INGEST Application Status as Rollback Active or Rollback in progress. There are no deadlocks in the event monitor, no Lock timeouts, no increase in Lock waits and no Lock escalations in the database. Internal rollbacks are increasing but that also occurs while an INGEST is not executing. The db2diag.log shows STMM increasing Database_memory over the first few sequential INGEST executions but I have not observed STMM increasing Locklist. The INGEST rollbacks still persist when Database_memory reaches a steady state. The db2diag.log shows no errors while the INGEST is executing.
I tried tuning the INGEST with commit_count or commit_period and there appears to be no significant change in the rollback behavior.
Can anyone confirm the observed rollbacks are expected when using the INGEST utility?
If not, any comments on what may help reduce or eliminate these rollbacks?