How to terminate running of imp/exp and expdp/impdp Processes

Terminate the running of imp/exp and expdp/impdp processes method 1. Stop the EXP/IMP optimization speed to directly KILL the process, but first KILL the parent process and then KILL the child process, only KILL sub-processes, EXP/IMP will also execute the sample in the background: ps-ef | grep imp query pid, kill-9 pid, kill-9 ppid, 2. Stop EXPDP/IMPDP. Here, the KILL process cannot be simply used to handle the problem, because here is a JOB 1. The EXPDP/IMPDP parameter: ATTACH connects to the existing JOB, for example, ATTACH [= job name]. JOB_NAME can be queried through dba_datapump_jobs:

sql>select * from dba_datapump_jobsOWNER_NAME                     JOB_NAME                       OPERATION------------------------------ ------------------------------ ------------------------------------------------------------JOB_MODE                                                     STATE                              DEGREE ATTACHED_SESSIONS DATAPUMP_SESSIONS------------------------------------------------------------ ------------------------------ ---------- ----------------- -----------------SYSTEM                         SYS_EXPORT_FULL_01         EXPORTFULL                                                         EXECUTING                               1                 1                 3

 

Example 1: C: \ Documents ents and Settings \ Administrator> expdp system/sys attach = SYS_EXPORT_FULL_01 Export: Release 11.2.0.1.0-Production on Saturday July 13 23:53:55 2013 Copyright (c) 1982,200 9, oracle and/or its affiliates. all rights reserved. connect to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-Production With the Partitioning, OLAP, Data Mining and Real Application Testing options job: SYS_EXPORT _ FULL_01 owner: SYSTEM Operation: EXPORT creator permission: true guid: 7374DCC3E7D547B3B755865E4DB59F10 Start Time: Saturday, 13 August 13, 2013 23:53:57 mode: FULL instance: tony maximum degree of Parallelism: 1 EXPORT job parameter: parameter Value: CLIENT_COMMAND system/******** directory = dir_dump dumpfile = dir_dump: bigtable. dmp logfile = dir_dump: bigtable. log full = y status: bytes processed by IDLING: 0 current concurrency: 1 job error count: 0 dump file: d: \ impdp \ bigtable. bytes written by dmp: 5,177,344 Worker 1 Status: process name: DW00 status: UNDEFIN ED Export> stop_job: Do you really want to stop this job ([Y]/N): Does y really want to stop this job ([Y]/N ): y: Do you really want to stop this job ([Y]/N): Does Y really want to stop this job ([Y]/N ): y: Do you really want to stop this JOB ([Y]/N): Y --------------- it cannot be stopped. You can still find the record in dba_datapump_jobs, but the JOB has stopped. ----- It has been solved. You need to enter YES Export> KILL_JOB to stop the job ([Y]/N): YES. During execution, CTL + C can enter the interaction mode, windows and LINUX are the same. Re-enter EXPDP/IMPDP to execute the following interactive command: $ expdp username/password. Common interactive mode commands: CONTINUE_CLIENT return to record mode. If the job is idle, the job is restarted. START_JOB starts and resumes the current job. When the default value (0) shows the new STATUS when available, the job STATUS is to be monitored at a frequency (in seconds. STATUS = [interval] STOP_JOB closes the executed job in sequence and exits the client. STOP_JOB = IMMEDIATE will immediately shut down the Data Pump job. There are other commands: ADD_FILE: Add a dump file to the dump set. ADD_FILE = dirobjdumpfile-name CONTINUE_CLIENT returns to record mode. If the job is idle, the job is restarted. EXIT_CLIENT exits the Client Session and keeps the job running. HELP summarizes interactive commands. KILL_JOB separates and deletes jobs. PARALLEL changes the number of active workers of the current job. PARALLEL = number of workers. START_JOB starts and resumes the current job. When the default value (0) shows the new STATUS when available, the job STATUS is to be monitored at a frequency (in seconds. STATUS = [interval] STOP_JOB closes the executed job in sequence and exits the client. STOP_JOB = IMMEDIATE will be closed immediately