First page Back Continue Last page Graphics
Data Pump Features…
Client can disconnect, reconnect at will
To monitor
- See STATUS and CONTINUE commands
To control
- STOP_JOB, KILL_JOB, change parallel degree (PARALLEL)
To restart jobs!
- See START_JOB
- Even after instance crash!
To add dump files
Notes:
Like original import / export, datapump provides command-line client software (impdp and expdp) that is run at the OS prompt.
Unlike the original utility, datapump clients can disconnect from the job (i.e. the background process performing the work). The client can then be reconnected to the job – see the ATTACH parameter on the impdp command. Reason to reattach to a job might be:
To monitor a long-running job. You may kick off a job, disconnect (ctrl+C followed by the EXIT_CLIENT command) and go to lunch. Upon your return, reconnect and check the status with the STATUS command.
To control a job. You may determine that the job is taking too much resources from the server. In this case, you can dynamically decrease the degree of parallelization with the PARALLEL command. (DOP can also be dynamically increased.) Or, you might temporarily halt the job with STOP_JOB and restart it later with START_JOB.
Yes, datapump jobs that fail can be restarted – as long as they get past the “DEFINE” stage – even if the instance crashes. I have tested this (in a test environment) and it worked as advertised.
If a job runs fails due to an exhausting the space in the dump file, you can add dump files for the job with the ADD_FILE command and restart the job.