Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. How to stop Oracle Data Pump job

    How to stop Oracle Data Pump job

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Additional Information
    • Article Type: General
    • Product: Aleph
    • Product Version: 19.01

    Description:
    Is there a way of killing Oracle Data Pump job, once it has started, in case of problems - running out of space is most likely?

    Resolution:
    To kill the job:

    ps -ef|grep dp
    kill [pid number]

    This will stop the job. Then you will need to clear the traces of the job from the database:

    1. Determine in SQL*Plus which Data Pump jobs exist in the database:
    -- locate Data Pump jobs:

    aleph_admin@ALEPH1> SELECT owner_name, job_name, operation, job_mode, state, attached_sessions FROM dba_datapump_jobs WHERE job_name NOT LIKE 'BIN$%' ORDER BY 1,2;
    **** Hit return to continue ****

    OWNER_NAME JOB_NAME
    ------------------------------ ------------------------------
    OPERATION
    ------------------------------------------------------------------------------------------
    JOB_MODE STATE
    ------------------------------------------------------------------------------------------ ---------------------- --------
    ATTACHED_SESSIONS
    -----------------
    ALEPH_ADMIN ABC01
    EXPORT
    TABLE NOT RUNNING
    0


    1 row selected.


    2. Ensure that the listed jobs in dba_datapump_jobs are not export/import Data Pump jobs that are active: status should be 'NOT RUNNING'.

    3. Check with the job owner that the job with status 'NOT RUNNING' in dba_datapump_jobs is not an export/import Data Pump job that has been temporary stopped, but is actually a job that failed.

    4. Determine in SQL*Plus the related master tables:

    aleph_admin@ALEPH1> SELECT o.status, o.object_id, o.object_type, o.owner||'.'||object_name "OWNER.OBJECT" FROM dba_objects o, dba_datapump_jobs j WHERE o.owner=j.owner_name AND o.object_name=j.job_name AND j.job_name NOT LIKE 'BIN$%' ORDER BY 4,2;
    **** Hit return to continue ****

    STATUS OBJECT_ID OBJECT_TYPE
    ------- ---------- -------------------
    OWNER.OBJECT
    -----------------------------------------------------------------------------------------------------------------------------------
    VALID 110176 TABLE
    ALEPH_ADMIN.ABC01

    1 row selected.

    5. For jobs that were stopped in the past and won't be restarted anymore, delete the master table. E.g.:

    aleph_admin@ALEPH1> DROP TABLE ALEPH_ADMIN.ABC01;

    Table dropped.

    Additional Information

    Oracle Data Pump kill dp


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • How to stop a serial item record from claiming
      • how to suppress 2nd call no. in brief record display
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 19.01
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved