Kill an expdp job

How can I kill an expdp job if I can not attach to it ? My job name is expdp_asdb and, when I try to attach to it with 'expdp attach=expdp_asdb', the system raises the next messages:
ORA-39002: invalid operation
ORA-39000: bad dump file specification
ORA-31640: unable to open dump file "/exportdb/exp_asdb/expdp_asdb.dmp" for read
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
When I look at the db for my job, this is the answer:
SQL> select * from dba_datapump_jobs
2 ;
OWNER_NAME JOB_NAME
OPERATION JOB_MODE
STATE DEGREE ATTACHED_SESSIONS
SYSTEM EXPDP_ASDB
EXPORT FULL
NOT RUNNING 0 0
Would anyone help me with this ?
Thanks in advance.
Sergio

ahh ok so when you submitted the job, what user did you use? An expdp job resides in the user's context e.g. you ran the job under userA, you need to run expdp userA/password attach

Similar Messages

How to schedule a expdp job on dbconsole 10g

Hi all,
is there any way to create a schedule expdp job to execute automatically all days on enterprise mananger 10g (dbconsole) ???
Thanks
Wander (Brazil)

Hi,
on dbconsol i get to schedule a job only to execute immediately or posteriorly, just one time, but I want that it run all day in a specific time.
Wander(Brazil)

How to find which user has killed a particular job in CPS?

Hi All,
I am new in CPS. I want to find the user who has killed a particular job in CPS?
Thanks in Advance.
Avdhesh

Hi Gerben,
Thanks for the reply.
But I noticed when I killed a job and checked in the last modified by option I didn't find my user name there. It was displaying the user who had modified that job definition last time.
Thank you
Avdhesh

How to kill a background job

Hi Experts,
I would like to ask on how to kill a background job in SAP? I have tried to cancel it via sm50, sm37, dpmon, and even the kill -9 command but none of those commands can solve the issue still the job is running.
Can you guide me on how to deal to such issue and if you know a command on how to kill that particular job.
Hoping for your immediate response.

Hi,
I think you may not have proper authorization to kill the job.
You can kill the job through SM50 as follows.
SM50 -> Choose the background job -> click Process -> and then click Cancel without core.
If the job is still not getting killed you can ask your basis person to kill it.
Regards
Vimal

Expdp job failure

We have two Oracle instance with exactly same configuration(memory etc..)
ORAA on Unix box 1, ORAB on Unix box 2 (both oracle 10g)
expdp job on both Instance was running fine. Now suddenly ORAB instance gives following error when expdp is run:
ORA-31626: job does not exist
ORA-31650: timeout waiting for master process response
Googled and searched forum, it says:
- Increase memory ( but expdp on ORAA is running ok with same memory config and same data size/dataset)
- Delete orphan jobs (dba_datapump_jobs shows 0 rows on both instance)
No access to metalink (oracle support). Any one with oracle know how, know of any tips to check or look into? It should be some simple fix (since ORAA is running fine).

31650, 00000, "timeout waiting for master process response"
// *Cause: After creating the job infrastructure and sending the initial
//          message to the master process, it failed to respond in the
//          allotted time and most likely aborted during startup.
// *Action: Retry the open or attach request. Contact Oracle Customer Support
//          if the problem persists.
bcm@bcm-laptop:~$ oerr ora 31626
31626, 00000, "job does not exist"
// *Cause: An invalid reference to a job which is no longer executing,
//          is not executing on the instance where the operation was
//          attempted, or that does not have a valid Master Table.
//          Refer to any following error messages for clarification.
// *Action: Start a new job, or attach to an existing job that has a
//          valid Master Table.

Recovering from failed expdp job

The following expdp job crashed because of network difficulties:
expdp fred parfile=fred_schema_export.par logfile=fred_export.log dumpfile=fred.dmp
Here is the parfile:
DIRECTORY=exp_dumps
SCHEMAS=fred
JOB_NAME=fred_schema_export_1
PARALLEL=2Here is the error I get when I try to rerun the job:
ORA-31626: job does not exist
ORA-31633: unable to create master table "FRED.FRED_SCHEMA_EXPORT_1"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 863
ORA-00955: name is already used by an existing objectHere are my questions:
* Is it safe to drop FRED.FRED_SCHEMA_EXPORT_1 (the "Master table")?
* To recover from the crash and restart the job, do I only have to drop that table? Or is there some other more sophisicated action I must perform?

Yes. Drop the table and restart the job.

Recommended/Widely followed way to kill a Datapump job

DB version: 11.2
OS : AIX/Solaris
What is the recommeded way to kill a currently running expdp or impdp job (dba_datapump_jobs.state = 'EXECUTING') ?
When I searched in google and OTN , i see different opinions and options.

Refer this
how to kill datapump jobs?
And
http://blog.oracle48.nl/killing-and-resuming-datapump-expdp-and-impdp-jobs/

I want to kill the background job.

HI all,
I have applied a job in background. it is taking too much of time to complete. Status is still ACTIVE only. i want to kill that job. how i need to do..
thanks

hi,
go to SM37 and click on your job and press cntrl+F1.
your active job will stop.
thanks,
Poonam

Speeding up the expdp job with PARALLEL and FILESIZE parameters

Daily we are going to back up 6 schemas with a total size of 80 GB.
From oracle documentation I gather that PARALLEL servers work well when we split the dump file because each slave process can work with a separate file.
But I am not sure how many parallel processes should be spawned and the how many files this dump file has to be split?
The expdp command we are planning to use
expdp userid=\'/ as sysdba\' SCHEMAS = schema1,schema2,schema3,schema4,schema5,schema6 DUMPFILE=composite_schemas_expdp.dmp LOGFILE=composite_schemas_expdp.log DIRECTORY=dpump_dir2 PARALLEL=3Related info:
11.2.0.2
Solaris 10 (x86_64) running on HP Proliant Machine
8 CPU with 32gb RAM
SQL > show parameter parallel
NAME                                 TYPE        VALUE
fast_start_parallel_rollback         string      LOW
parallel_adaptive_multi_user         boolean     TRUE
parallel_automatic_tuning            boolean     FALSE
parallel_degree_limit                string      CPU
parallel_degree_policy               string      MANUAL
parallel_execution_message_size      integer     16384
parallel_force_local                 boolean     TRUE
parallel_instance_group              string
parallel_io_cap_enabled              boolean     FALSE
parallel_max_servers                 integer     32
parallel_min_percent                 integer     0
NAME                                 TYPE        VALUE
parallel_min_servers                 integer     0
parallel_min_time_threshold          string      AUTO
parallel_server                      boolean     TRUE
parallel_server_instances            integer     2
parallel_servers_target              integer     32
parallel_threads_per_cpu             integer     2
recovery_parallelism                 integer     0

I just did a test export of a 16gb schema (schema size confirmed from dba_segments).
I didn't specify the FILESIZE parameter. Instead I specified PARALLEL = 5 with DUMPFILE=tstschema_expdp%U.dmp hoping that expdp will create 5 different dumpfiles for the 5 slave processes to work with. But expdp created only 4 files.
Export: Release 11.2.0.1.0 - Production on Mon Aug 6 10:30:57 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "EXPIMP_USER"."SYS_EXPORT_SCHEMA_01": expimp_user/******** SCHEMAS = TSTSCHEMA DUMPFILE=tstschema_expdp%U.dmp LOGFILE=test_expdp.log DIRECTORY=dpump_dir PARALLEL=5
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 9.089 GB
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
. . exported "TSTSCHEMA"."FTB_RES_RCS"                      14.75 MB   13860 rows
Processing object type SCHEMA_EXPORT/SYNONYM/SYNONYM
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
. . exported "TSTSCHEMA"."CASR_HAP_DTL"                      824.9 MB 1613143 rows
. . exported "TSTSCHEMA"."JOHN"                                  0 KB       0 rows
. . exported "TSTSCHEMA"."DCVERSO"                           7.210 GB 7502854 rows
Master table "EXPIMP_USER"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
Dump file set for EXPIMP_USER.SYS_EXPORT_SCHEMA_01 is:
/u05/bkp_DUMP/tstschema_expdp01.dmp
/u05/bkp_DUMP/tstschema_expdp02.dmp
/u05/bkp_DUMP/tstschema_expdp03.dmp
/u05/bkp_DUMP/tstschema_expdp04.dmp
Job "EXPIMP_USER"."SYS_EXPORT_SCHEMA_01" successfully completed at 11:07:36My conclusion:
If you want to keep Number of dumpfiles to be generated and Number of Parallel processes to be N (same) then use FILESIZE
ie.
Say you want to export an 80gb schema and if you setting PARALLEL = 5 , it is better to specify FILESIZE after doing the arithmetic.
Divide 80/5 = 16 . So put the FILESIZE = 16g so that expdp will create 5 different files to 5 different 5 slave processes to work with.

How to kill a print job?

For some reason, I have a print job that is printing endless blank pages.
It no longer appears in the printer's print queue. how do i delete it?

Is there a way of pausing the printer, and sending $1B $45 to the printer? It's only 2 bytes, for crying out loud. Sheeeeesh. It's bugs like this that make the Mac look bad.
Don't know and never cared. Maybe somebody has done some research along these lines. I haven't really needed anything like this since the Print Screen button quit working when we went to Windows and System 7 (yeah, it's a copy screen button now).
It would seem that you would need some kind of command line program running, or maybe an applescript or automator action. Then you would also have to be able to ensure that your model of the hundreds of available printers from all the brands actually honor or respond to the code at all or in time to be of any use. In addition, I'd assume that the configuration of the printer (local, network, IPP, shared with Mac, shared with Windows etc) could affect the required code or syntax.
If there is a feature missing in an OS, then it's not really a 'bug'. That's a pretty loose description to use. That's like saying that not having a 'print' button on a keyboard is a bug. It's a feature I'd like (but probably get in trouble with), but I've never taken the time to map a key combo for it. If I wanted to, I'd probably install Quickeys again like back in the '90s.
Meanwhile, I try to keep it simple, I just turn around, face the printer with a glare, and flip the switch. No code to remember, no command line or script to run, no argument or delay's from the printer. Our best network printer is within a couple of feet of my desk
I'll just bet this thread brings up a bunch of methods that can cancel a print. Including at least 2 or 3 terminal commands and a script or two. Here's one video demo on how to write a script to cancel printing: http://www.youtube.com/watch?v=xH0Yami9_0&feature=PlayList&p=1512FA817EBBF876&playnext=1&playnextfrom=PL&index=19 - I didn't bother to actually do this. Too many Mac's to worry with.
Problem is, I won't remember it when I need it. Killing the power is so satisfying and proactive.

Kill last reports job with web.show_documents ?

Hi,
I call the Reports service for creating PDF - reports from a Forms modul ,
after creating the report I kill this last Report-job with web.show_document but get the xml response in a new browser window.
Is there another method to send the Report request from Forms without opening this second browser window incl. response data ?
(e.g. a atomic security bundle: Show report result & kill the job ..)
Many thanks
F.

Eventually , the report run... when the active thread got the value 1. How is it done...(i mean the value of 1 , instead of 2 when the report started...????) How to secure that the active thread would be 1 if this is the problem...????
However , because the report is 2 page accross.... the report displays the first page and down the other page.... Is it possible to display both pages accross as i see them in report builder env....?????
Thanks , a lot
Simon

How shall I cancel /kill the Batch job that is to be scheduled daily in BI.

Hello Experts,
We have a background batch job used to trigger an event to execute the Porcess Chain that is to be scheduled daily in BI.
Now we don't required this functionality any more.So I try to cancel this job using transaction SM37 but unfortunately I am not able to cancel/ kill the job.
How shall I handle this issue.
any suggestions please.
Thanks & regards

Hi
Select your process chain in the planning view
Right click on the start varaint and display all jobs,
It will show you the job scheduled, Finshed everything.
Select the job which is scheduled or released and Delete the job.
Else go to SM37 , enter the job, delete the scheduled job there.
Regards
M.A

Unable to kill a DBMS job.

Hi there,
Using Oracle 11.1.0.6.0 on Windows 2008 R2.
Being a novice, i need advice on the below:
A developer had created this job on our database and i've been trying to delete this job for good but cant. Tried DBMS_JOB.REMOVE & setting job BROKEN=Y but for some reason it automatically generates a new JOB ID or resets the job BROKEN=N. Is there another way?
Many thanks!
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job => X
,what => 'dbms_refresh.refresh(''"DEV"."SUBMISSIONS"'');'
,next_date => to_date('01/01/4000 00:00:00','dd/mm/yyyy hh24:mi:ss')
,interval => 'SYSDATE+1/24 '
,no_parse => FALSE
Edited by: 943209 on 31-Aug-2012 07:17

The DBMS_JOB package is an interface to the SYS.JOB$ table. The Submit() call for example does a SQL insert. Breaking a job is a SQL update. Removing a job is a SQL delete.
An explicit commit is needed to make the SQL change to this table permanent.
What a break/remove call does not do however, is kill and remove the job queue process that may be busy executing that job. If there is such a process, deleting/breaking the job does not affect the process. The process needs to be identified and killed (e.g. using the ALTER SYSTEM KILL SESSION command).
The job queue manager does NOT start broken jobs automatically. You need to explicitly execute that job using the Run() call - in which case a successful job completion will result in the job entry in the table to updated and unbroken.
The job queue manager CANNOT start a job that has been deleted/removed from the job table. No row. No job.
So if the job appears to become active again - then you have another process that recreates that job using the Submit() call. And that is the process you need to "fix" to prevent the job from reappearing again as a running jobs after the job entry was broken or removed.

EXPDP Job Monitor

View Select * from dba_datapump_jobs hangs any possible cause or any other query to check the status of the job ?

You can see the progress in v$session_longops querying the sofar and totalwork columns.

Kill Users Batch job

Hi,
Oracle 11g
Windows/Unix
I have a program that kill all users before doing export dump.
This is the select statement that will spool to kill_user.sql
select 'alter system kill session '||''''||sid||','||serial#||''';' from v$session where type='USER';This program is placed scheduled task for windows or crontab for unix.
My problem is, how can I exempt the owner(sched task) of the program from being killed?
You know that it will be included in the list at the time the select statement is run, right?
And I might happen that it is the first one to get killed, which results to not killing all rest of the users. Is my logic right?
Please help....
Thanks

Hello,
I have a program that kill all users before doing export dump.
well, just sample one..but there are lots of usage for killing users May be, but what is the aim of this ? If you intend to get a consistent Export, you have other solutions.
For instance, with the Original Export/Import you may use the parameter CONSISTENT=Y:
http://download.oracle.com/docs/cd/E11882_01/server.112/e16536/original_export.htm#SUTIL2672
If you use the DATAPUMP Export/Import you may use the parameter FLASHBACK_SCN or FLASHBACK_TIME:
http://download.oracle.com/docs/cd/E11882_01/server.112/e16536/dp_export.htm#i1007149
http://download.oracle.com/docs/cd/E11882_01/server.112/e16536/dp_export.htm#i1007150
Hope this help.
Best regards,
Jean-Valentin

Kill an expdp job

Similar Messages

Maybe you are looking for