在使用expdp导出一个表的数据时遇到了下面情况，也不见其提示报错信息，一下子就执行完了，也没有导出我需要的数据
[oracle@getlnx01 dump_dir]$ expdp system/xxxx TABLES=xxx.inv_workshop_stock dumpfile=inv_workshop_stock.dmp DIRECTORY=DUMP_DIR logfile=1.log;
Export: Release 10.2.0.4.0 - 64bit Production on Wednesday, 15 April, 2015 22:13:12
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
检查告警日志后发现有如下错误信息
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=54, OS id=7773
to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_TABLE_01', 'SYSTEM', 'KUPC$C_1_20150415221312', 'KUPC$S_1_20150415221312', 0);
more /u01/app/oracle/admin/epps/bdump/epps_j000_15958.trc
/u01/app/oracle/admin/epps/bdump/epps_j000_15958.trc
Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name: Linux
Node name: getlnx01.esqule.com
Release: 2.6.32-200.13.1.el5uek
Version: #1 SMP Wed Jul 27 21:02:33 EDT 2011
Machine: x86_64
Instance name: epps
Redo thread mounted by this instance: 1
Oracle process number: 49
Unix process pid: 15958, image: oracle@getlnx01.esqule.com (J000)
*** ACTION NAME:(AUTO_SPACE_ADVISOR_JOB) 2015-04-09 22:00:05.661
*** MODULE NAME:(DBMS_SCHEDULER) 2015-04-09 22:00:05.661
*** SERVICE NAME:(SYS$USERS) 2015-04-09 22:00:05.661
*** CLIENT ID:() 2015-04-09 22:00:05.661
*** SESSION ID:(1313.553) 2015-04-09 22:00:05.661
*** 2015-04-09 22:00:05.661
ORA-12012: error on auto execute of job 8887
ORA-01157: cannot identify/lock data file ORA-01157: cannot identify/lock data file 206 - see DBWR trace file
ORA-01110: data file 206: '/u04/epps/oradata/temp02.dbf'
ORA-06512: at "SYS.PRVT_ADVISOR", line 1624
ORA-06512: at "SYS.DBMS_ADVISOR", line 186
ORA-06512: at "SYS.DBMS_SPACE", line 1500
ORA-06512: at "SYS.DBMS_SPACE", line 1566
如上所示，在出现The value (30) of MAXTRANS parameter ignored错误的同时也出现了ORA-01157 & ORA-01110错误，可以参考ORA-01157 & ORA-01110博客，出现这个问题是因为在测试环境使用RMAN还原了数据库（32bit还原升级到64bit），在expdp导出时，需要使用临时表空间，由于临时表空间问题导致expdp异常终止了。解决了这个问题后，数据泵就能成功导出数据了。
