Datapump Job Can Not Be Stopped or Dropped
(Doc ID 2571841.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
Datapump job cannot be stopped or dropped even after following the steps from <Document 336014.1> - How To Cleanup Orphaned DataPump Jobs In DBA_DATAPUMP_JOBS ?>
Running a select from dba_datapump_jobs to check the job status, the following information is found:
SQL> SELECT owner_name, job_name, rtrim(operation) "OPERATION", rtrim(job_mode) "JOB_MODE", state, attached_sessions
FROM dba_datapump_jobs
WHERE job_name NOT LIKE 'BIN$%'
ORDER BY 1,2;
OWNER_NAME JOB_NAME OPERATION JOB_MODE STATE ATTACHED_SESSIONS
---------- -------------------- ------------ ------------ ------------ -----------------
SYS SYS_IMPORT_TABLE_01 IMPORT TABLE STOPPING 0
FROM dba_datapump_jobs
WHERE job_name NOT LIKE 'BIN$%'
ORDER BY 1,2;
OWNER_NAME JOB_NAME OPERATION JOB_MODE STATE ATTACHED_SESSIONS
---------- -------------------- ------------ ------------ ------------ -----------------
SYS SYS_IMPORT_TABLE_01 IMPORT TABLE STOPPING 0
No new IMPDP Jobs are possible.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |