Database Reference
In-Depth Information
Data Dictionary Views
A quick way to determine whether a Data Pump job is running is to check the DBA_DATAPUMP_JOBS view for anything
running with a STATE that has an EXECUTING status:
select job_name, operation, job_mode, state
from dba_datapump_jobs;
Here is some sample output:
JOB_NAME OPERATION JOB_MODE STATE
------------------------- -------------------- ---------- ---------------
SYS_IMPORT_TABLE_04 IMPORT TABLE EXECUTING
SYS_IMPORT_FULL_02 IMPORT FULL NOT RUNNING
You can also query the DBA_DATAPUMP_SESSIONS view for session information via the following query:
select sid, serial#, username, process, program
from v$session s,
dba_datapump_sessions d
where s.saddr = d.saddr;
Here is some sample output, showing that several Data Pump sessions are in use:
SID SERIAL# USERNAME PROCESS PROGRAM
---------- ---------- -------------------- --------------- ----------------------
1049 6451 STAGING 11306 oracle@xengdb (DM00)
1058 33126 STAGING 11338 oracle@xengdb (DW01)
1048 50508 STAGING 11396 oracle@xengdb (DW02)
Database Alert Log
If a job is taking much longer than you expected, look in the database alert log for any messages similar to this:
statement in resumable session 'SYS_IMPORT_SCHEMA_02.1' was suspended due to
ORA-01652: unable to extend temp segment by 64 in tablespace REG_TBSP_3
This message indicates that a Data Pump import job is suspended and is waiting for space to be added to the
REG_TBSP_3 tablespace. After you add space to the tablespace, the Data Pump job automatically resumes processing.
By default a Data Pump job waits 2 hours for space to be added.
In addition to writing to the alert log, for each Data pump job, Oracle creates a trace file in the ADR_HOME/trace
directory. this file contains information such as the session ID and when the job started. the trace file is named with the
following format: <SID>_dm00_<process_ID>.trc .
Note
 
 
Search WWH ::




Custom Search