Slow performance if a running job is stopped

Whenever a job is stopped such as an import or export job, the database system must roll back the complete transaction to bring the database to a consistent state.

Symptoms

This rollback process uses maximum system resources such as CPU time and memory.

Resolving the problem

Wait until the rollback completes and the system returns to a normal state. Do not stop a running job unless necessary.