【译】Export/Import DataPump Parameter TRACE - How to Diagnose Oracle Data Pump [ID 286496.1]

In this Document
  Purpose
  Scope and Application
  Export/Import DataPump Parameter TRACE - How to Diagnose Oracle Data Pump
     1. Introduction.
     2. How to create a Data Pump trace file ?  Parameter: TRACE
     3. How to start tracing the Data Pump job ?
     4. How are Data Pump trace files named, and where to find them ?
     5. How to get a detailed status report of a Data Pump job ?  Parameter: STATUS
     6. How to get timing details on processed objects ? Parameter: METRICS
     7. How to get SQL trace files of the Data Pump processes ?
     8. How to get header details of Export Data Pump dumpfiles ?
     9. How to get Data Definition Language (DDL) statements ? Parameter: SQLFILE
     10. How to get the DDL both as SQL statements and as XML data ?
     @ 11. How to get a copy of the master table ?  Parameter: KEEP_MASTER
     @ 12. For Support: Diagnostic techniques.
  References

 

--------------------------------------------------------------------------------

 

Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.1.0.6 - Release: 10.1 to 11.1
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.1.0.6   [Release: 10.1 to 11.1]
Oracle Server - Personal Edition - Version: 10.1.0.2 to 11.1.0.6   [Release: 10.1 to 11.1]
Oracle Server - Standard Edition - Version: 10.1.0.2 to 11.1.0.6   [Release: 10.1 to 11.1]
Enterprise Manager for RDBMS - Version: 10.1.0.2 to 11.1   [Release: 10.1 to ]
Information in this document applies to any platform.

Purpose
This document describes how to use the TRACE parameter with the Export Data Pump (expdp) and Import Data Pump (impdp) database utilities when diagnosing incorrect behavior and/or troubleshooting Data Pump errors.

Scope and Application
The article is intended for users of the database utilities Export Data Pump (expdp) and Import Data Pump (impdp), and who need to troubleshoot the execution of the jobs that are generated by these utilities. These database utilities were introduced with Oracle10g. The article gives detailed information how to use the undocumented parameter TRACE.
Export/Import DataPump Parameter TRACE - How to Diagnose Oracle Data Pump

1. Introduction.
In Oracle10g, we introduced the new database utilities Export Data Pump and Import Data Pump.
Data Pump jobs use a master table, a master process, and worker processes to perform the work and keep track of the progress. For every Data Pump Export job and Data Pump Import job, a master process is created. The master process controls the entire job, including communicating with the clients, creating and controlling a pool of worker processes, and performing logging operations.
Example output when a full database Export Data Pump is running with parallelism 2:

% expdp system/manager DIRECTORY=my_dir DUMPFILE=expdp_f%U.dmp /
LOGFILE=expdp_f.log FULL=y PARALLEL=2

% ps -ef | grep expdp
oracle    8874  8704  1 07:00 pts/2    00:00:03 expdp                DIRECTORY=my_dir ...

% ps -ef | grep ORCL
oracle    8875  8874  4 07:00 ?        00:00:11 oracleORCL (DESCRIPTION=(LOCAL=YES) ... 
oracle    8879     1  3 07:00 ?        00:00:08 ora_dm00_ORCL 
oracle    8881     1 94 07:00 ?        00:04:17 ora_dw01_ORCL 
oracle    8893     1  3 07:00 ?        00:00:09 ora_dw02_ORCL 
...

-- Obtain Data Pump process info:
set lines 150 pages 100 numwidth 7
col program for a38
col username for a10
col spid for a7
select to_char(sysdate,'YYYY-MM-DD HH24:MI:SS') "DATE", s.program, s.sid,  
       s.status, s.username, d.job_name, p.spid, s.serial#, p.pid  
  from v$session s, v$process p, dba_datapump_sessions d 
 where p.addr=s.paddr and s.saddr=d.saddr; 

DATE                PROGRAM                                    SID STATUS
------------------- -------------------------------------- ------- --------
2007-10-19 07:01:03 ude@celclnx7.us.oracle.com (TNS V1-V3)     140 ACTIVE
2007-10-19 07:01:03 oracle@celclnx7.us.oracle.com (DM00)       152 ACTIVE
2007-10-19 07:01:03 oracle@celclnx7.us.oracle.com (DW01)       144 ACTIVE
2007-10-19 07:01:03 oracle@celclnx7.us.oracle.com (DW02)       159 ACTIVE

USERNAME   JOB_NAME                       SPID    SERIAL#     PID
---------- ------------------------------ ------- ------- -------
SYSTEM     SYS_EXPORT_FULL_01             8875          8      18
SYSTEM     SYS_EXPORT_FULL_01             8879         21      21
SYSTEM     SYS_EXPORT_FULL_01             8881          7      22
SYSTEM     SYS_EXPORT_FULL_01             8893         26      23
The Data Pump processes will disappear when the Data Pump job completes or is (temporary) stopped.
Improved tracing capabilities have been implemented with these utilities. The tracing can be controlled with the TRACE parameter.

Data Pump is server based and not client based. This means that most Data Pump specific defects will be fixed on the server side (changes in packages in source and target database) and not on the client side (Export or Import Data Pump client). If a Data Pump defect that occurs during an import job is fixed in a later patchset (e.g. 10.2.0.4.0) and the target database is still on the base release (10.2.0.1.0) then the defect will still occur when importing with a 10.2.0.4.0 Import Data Pump client into this 10.2.0.1.0 target database. The same applies to export jobs. It is therefore recommended that both the source database and the target database have the latest patchset installed. For details, see also:
Note:553337.1 "Export/Import DataPump Parameter VERSION - Compatibility of Data Pump Between Different Oracle Versions"

 

2. How to create a Data Pump trace file ?  Parameter: TRACE

Tracing can be enabled by specifying an 7 digit hexadecimal mask in the TRACE parameter of Export DataPump (expdp) or Import DataPump (impdp). The first three digits enable tracing for a specific Data Pump component, while the last four digits are usually: 0300.
Any leading zero's can be omitted, and the value specified for the TRACE parameter is not case sensitive.
Example:

 

在数据泵工具(expdp/impdp)工具里有个 TRACE 参数，可以设置一个7位16进制数来开启跟踪功能(Tracing)。该参数前3位指定data pump 组件，后4位始终是 0300。

任何前导零都会被忽略，而且该参数值是不区分大小写的。

例如：

 

TRACE = 04A0300

-- or:

TRACE=4a0300

 

Some rules to remember when specifying a value for the TRACE parameter:
- do not specify more than 7 hexadecimal digits;
- do not specify the typical leading 0x hexadecimal specification characters;
- do not convert the hexadecimal value to a decimal value;
- omit any leading zero's (not required though);
- values are not case sensitive.