My Oracle Support Banner

After Issuing STOP_JOB=IMMEDIATE For an In Progress Data Pump Import Job, Massive Rollback and Application Latency Noted - Implications of Running START_JOB (Doc ID 2731580.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


On Oracle version, a Data Pump Import job was started to restore data to a large (250G) table that was accidentally truncated. The syntax used was:

impdp dumpfile=TABLE_%U.dmp logfile=TABLE.log directory=data_pump_dir parallel=16 table_exists_action=APPEND

This was started while the database was busy, and growing application latency was noted after the import was kicked off. Therefore the impdp job then was stopped with STOP_JOB=IMMEDIATE with the intention of 'pausing' the job until a less busy time. However, when the START_JOB command was issued later, nothing seemed to happen for many hours other than observing high CPU for Data Pump processes and a growing amount of rollback segments in the undo tablespace. There was no discernible progress with the Data Pump Import.

None of the data inserted by Data Pump since the start of the job was visible from any other session.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.