Oracle DBA Tips and Techniques

By Arjun Raja

DATAPUMP – KILL JOBS ONLY USING THE DATAPUMP TOOL.

Posted by Arjun Raja on July 12, 2011

Killing an expdp or impdp process from the oslevel will not stop the job – so expdp or impdp jobs must be killed from the database level.

Example ?

Start an import job…..

Check the dba_datapump_jobs view…

sql > select job_name,state from dba_datapump_jobs;

Look for your job –

Job: SYS_IMPORT_SCHEMA_01

Owner: SYSTEM

Operation: IMPORT

Creator Privs: TRUE

GUID: A5E1F1E133EB0030E0430A35C8EC0030

Start Time: Friday, 17 June, 2011 12:37:39

Mode: SCHEMA

Instance: cmi1d

Max Parallelism: 1

EXPORT Job Parameters:

CLIENT_COMMAND system/******** directory=cmid schemas=EBS_FA_ARCHIVE dumpfile=ebs_fa.dmp logfile=ebsfa.log

IMPORT Job Parameters:

Parameter Name Parameter Value:

CLIENT_COMMAND system/******** schemas=ebs_fa_archive dumpfile=ebs_fa.dmp logfile=ebs_fa.log directory=cmid table_exists_action=replace

TABLE_EXISTS_ACTION REPLACE

State: EXECUTING

Bytes Processed: 1,022,819,072

Percent Done: 46

Current Parallelism: 1

Job Error Count: 0

Dump File: /u02/oradata/export/ebs_fa.dmp

Worker 1 Status:

Process Name: DW02

State: EXECUTING

Object Schema: EBS_FA_ARCHIVE

Object Name: FA_ASSETS_N1

Object Type: SCHEMA_EXPORT/TABLE/INDEX/INDEX

Worker Parallelism: 1

Import> KILL_JOB

Are you sure you wish to stop this job ([yes]/no): yes

When attaching a job -make sure you login with same user as user who ran the job.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: