<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Cleanup Oracle Datapump Import Jobs?</title>
	<atom:link href="http://www.dbuggr.com/kpalati/cleanup-oracle-datapump-import-jobs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbuggr.com/kpalati/cleanup-oracle-datapump-import-jobs/</link>
	<description>Share Knowledge &#38; Be Rewarded</description>
	<lastBuildDate>Fri, 03 Feb 2012 23:13:48 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: kpalati</title>
		<link>http://www.dbuggr.com/kpalati/cleanup-oracle-datapump-import-jobs/comment-page-1/#comment-130</link>
		<dc:creator>kpalati</dc:creator>
		<pubDate>Tue, 27 Oct 2009 04:31:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbuggr.com/kpalati/cleanup-oracle-datapump-import-jobs/#comment-130</guid>
		<description>Occasionally we might want to kill a long running Oracle import jobs ,we do it using &lt;strong&gt;kill -p  &lt;/strong&gt; But when this (kill -p) is done for a datapump job, it doesn&#039;t completely kill the job and locks up the underlying db objects. To resolve this, you must attach to a datapump job and use kill_job

UNIX\&gt; sqlplus &#039;/as sysdba&#039;

SQL&gt; select job_name, state from dba_datapump_jobs;

JOB_NAME                       STATE
------------------------------ ------------------------------
SYS_IMPORT_SCHEMA_01           NOT RUNNING

SQL&gt; exit

UNIX\&gt; impdp \&#039;sys/aa as sysdba\&#039; attach=SYS_IMPORT_SCHEMA_01

IMPORT&gt; STATUS    --&gt; This shows the status of your job

IMPORT&gt;  KILL_JOB --&gt; This will kill the datapump job and remove the underlying base tables

START_JOB, STOP_JOB, EXIT_CLIENT are few other options while using datapump. 

impdp help=y   or   expdp help=y lists all of them

Due to some locking conditions, if you are not able to kill the job using above method, you can also drop the datapump master table - pls make sure you are dropping the right table as this is irreversible. 

UNIX\&gt; sqlplus &#039;/as sysdba&#039;
SQL&gt; drop table SYS_IMPORT_SCHEMA_01;
SQL&gt; exit</description>
		<content:encoded><![CDATA[<p>Occasionally we might want to kill a long running Oracle import jobs ,we do it using <strong>kill -p  </strong> But when this (kill -p) is done for a datapump job, it doesn&#8217;t completely kill the job and locks up the underlying db objects. To resolve this, you must attach to a datapump job and use kill_job</p>
<p>UNIX\&gt; sqlplus &#8216;/as sysdba&#8217;</p>
<p>SQL&gt; select job_name, state from dba_datapump_jobs;</p>
<p>JOB_NAME                       STATE<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212; &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
SYS_IMPORT_SCHEMA_01           NOT RUNNING</p>
<p>SQL&gt; exit</p>
<p>UNIX\&gt; impdp \&#8217;sys/aa as sysdba\&#8217; attach=SYS_IMPORT_SCHEMA_01</p>
<p>IMPORT&gt; STATUS    &#8211;&gt; This shows the status of your job</p>
<p>IMPORT&gt;  KILL_JOB &#8211;&gt; This will kill the datapump job and remove the underlying base tables</p>
<p>START_JOB, STOP_JOB, EXIT_CLIENT are few other options while using datapump. </p>
<p>impdp help=y   or   expdp help=y lists all of them</p>
<p>Due to some locking conditions, if you are not able to kill the job using above method, you can also drop the datapump master table &#8211; pls make sure you are dropping the right table as this is irreversible. </p>
<p>UNIX\&gt; sqlplus &#8216;/as sysdba&#8217;<br />
SQL&gt; drop table SYS_IMPORT_SCHEMA_01;<br />
SQL&gt; exit</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
