[oracle@rac1 log]$ expdp test/test directory=DATA_PUMP_DIR dumpfile=test%U.dmp logfile=test_b.log tables=B flashback_scn=14298
Export: Release 11.2.0.4.0 - Production on Sat Jan 13 17:19:37 2018
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Starting "TEST"."SYS_EXPORT_TABLE_01": test/******** directory=DATA_PUMP_DIR dumpfile=test%U.dmp logfile=test_b.log tables=B flashback_scn=14298
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 64 KB
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-31693: Table data object "TEST"."B" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01466: unable to read data - table definition has changed
Master table "TEST"."SYS_EXPORT_TABLE_01" successfully loaded/unloaded
******************************************************************************
Dump file set for TEST.SYS_EXPORT_TABLE_01 is:
/u02/app/oracle/product/11.2.0/db_home/rdbms/log/test01.dmp
Job "TEST"."SYS_EXPORT_TABLE_01" completed with 1 error(s) at Sat Jan 13 17:20:47 2018 elapsed 0 00:01:05
[oracle@rac1 log]$ ls
dp.log orcl1_ora_16096.trc test01.dmp test_b.log
[oracle@rac1 log]$ rm -rf *
[oracle@rac1 log]$
重启数据库后再次执行导出仍然报错
参考如下MOS文章,检查不匹配:
ORA-1466 Raised by Data Pump Export on Master Table (文档 ID 2088236.1)
How To Cleanup Orphaned DataPump Jobs In DBA_DATAPUMP_JOBS ? (文档 ID 336014.1)
检查结果如下:
SQL> CONNECT / as sysdba
SET lines 200
COL owner_name FORMAT a10;
COL job_name FORMAT a20
Connected.
SQL> SQL> COL state FORMAT a12
SQL> SQL> SQL> COL operation LIKE state
SQL> COL job_mode LIKE state
SQL> COL owner.object for a50
SQL>
SQL> -- locate Data Pump jobs:
SQL>
SQL> SELECT owner_name, job_name, rtrim(operation) "OPERATION",
2 rtrim(job_mode) "JOB_MODE", state, attached_sessions
3 FROM dba_datapump_jobs
4 WHERE job_name NOT LIKE 'BIN$%'
5 ORDER BY 1,2;
no rows selected
SQL> set linesize 200 trimspool on
SQL> set pagesize 2000
SQL> col owner form a30
SQL> col created form a25
SQL> col last_ddl_time form a25
SQL> col object_name form a30
SQL> col object_type form a25
SQL> select OWNER,OBJECT_NAME,OBJECT_TYPE, status,
2 to_char(CREATED,'dd-mon-yyyy hh24:mi:ss') created ,to_char(LAST_DDL_TIME , 'dd-mon-yyyy hh24:mi:ss') last_ddl_time
3 from dba_objects
4 where object_name like 'ET$%'
5 /
no rows selected
SQL>
SQL> select owner, TABLE_NAME, DEFAULT_DIRECTORY_NAME, ACCESS_TYPE
2 from dba_external_tables
3 order by 1,2
4 /
no rows selected
根据如下MOS文章,可判断为BUG:
ORA-31693 ORA-1466 Errors During Datapump Export Using Flashback (文档 ID 1072871.1)
In this Document
Symptoms
Changes
Cause
Solution
References
APPLIES TO:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.2 [Release 10.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 14-Nov-2017***
SYMPTOMS
Datapump export raises the following errors:
ORA-31693: Table data object "<schema>"."RE$ACTION_IMP_TAB" failed to load/unload and is being skipped due to error:
ORA-01466: unable to read data - table definition has changed
CHANGES
Datapump expdp is being used with the FLASHBACK_TIME or FLASHBACK_SCN options specified.
CAUSE
The issue is addressed in
Bug 9110642 - ORA-1466 using EXPDP with FLASHBACK_TIME option using SYSDATE
The issue may particularly arise when SYSDATE is being referenced for the FLASHBACK_TIME
The bug is fixed in
12.1.0.1 (Base Release)
11.2.0.3 (Server Patch Set)
Please refer to
Note 9110642.8 - Bug 9110642 - ORA-1466 using EXPDP with FLASHBACK_TIME option using SYSDATE
SOLUTION
To solve the issue, use any of below alternatives:
o Upgrade to 12c
- OR -
o Apply patch set 11.2.0.3 or higher
- OR -
o Apply interim Patch 9110642 if available for your platform and (PSU) patch level
To check for conflicting patches, please use the MOS Patch Planner Tool
Please refer to
Note 1317012.1 - How To Use MOS Patch Planner To Check And Request The Conflict Patches?
- OR -
o As a workaround
- Do not use the FLASHBACK_TIME or FLASHBACK_SCN options
- Use the original export/import.
Export: Release 11.2.0.4.0 - Production on Sat Jan 13 17:19:37 2018
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Starting "TEST"."SYS_EXPORT_TABLE_01": test/******** directory=DATA_PUMP_DIR dumpfile=test%U.dmp logfile=test_b.log tables=B flashback_scn=14298
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 64 KB
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-31693: Table data object "TEST"."B" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01466: unable to read data - table definition has changed
Master table "TEST"."SYS_EXPORT_TABLE_01" successfully loaded/unloaded
******************************************************************************
Dump file set for TEST.SYS_EXPORT_TABLE_01 is:
/u02/app/oracle/product/11.2.0/db_home/rdbms/log/test01.dmp
Job "TEST"."SYS_EXPORT_TABLE_01" completed with 1 error(s) at Sat Jan 13 17:20:47 2018 elapsed 0 00:01:05
[oracle@rac1 log]$ ls
dp.log orcl1_ora_16096.trc test01.dmp test_b.log
[oracle@rac1 log]$ rm -rf *
[oracle@rac1 log]$
重启数据库后再次执行导出仍然报错
参考如下MOS文章,检查不匹配:
ORA-1466 Raised by Data Pump Export on Master Table (文档 ID 2088236.1)
How To Cleanup Orphaned DataPump Jobs In DBA_DATAPUMP_JOBS ? (文档 ID 336014.1)
检查结果如下:
SQL> CONNECT / as sysdba
SET lines 200
COL owner_name FORMAT a10;
COL job_name FORMAT a20
Connected.
SQL> SQL> COL state FORMAT a12
SQL> SQL> SQL> COL operation LIKE state
SQL> COL job_mode LIKE state
SQL> COL owner.object for a50
SQL>
SQL> -- locate Data Pump jobs:
SQL>
SQL> SELECT owner_name, job_name, rtrim(operation) "OPERATION",
2 rtrim(job_mode) "JOB_MODE", state, attached_sessions
3 FROM dba_datapump_jobs
4 WHERE job_name NOT LIKE 'BIN$%'
5 ORDER BY 1,2;
no rows selected
SQL> set linesize 200 trimspool on
SQL> set pagesize 2000
SQL> col owner form a30
SQL> col created form a25
SQL> col last_ddl_time form a25
SQL> col object_name form a30
SQL> col object_type form a25
SQL> select OWNER,OBJECT_NAME,OBJECT_TYPE, status,
2 to_char(CREATED,'dd-mon-yyyy hh24:mi:ss') created ,to_char(LAST_DDL_TIME , 'dd-mon-yyyy hh24:mi:ss') last_ddl_time
3 from dba_objects
4 where object_name like 'ET$%'
5 /
no rows selected
SQL>
SQL> select owner, TABLE_NAME, DEFAULT_DIRECTORY_NAME, ACCESS_TYPE
2 from dba_external_tables
3 order by 1,2
4 /
no rows selected
根据如下MOS文章,可判断为BUG:
ORA-31693 ORA-1466 Errors During Datapump Export Using Flashback (文档 ID 1072871.1)
In this Document
Symptoms
Changes
Cause
Solution
References
APPLIES TO:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.2 [Release 10.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 14-Nov-2017***
SYMPTOMS
Datapump export raises the following errors:
ORA-31693: Table data object "<schema>"."RE$ACTION_IMP_TAB" failed to load/unload and is being skipped due to error:
ORA-01466: unable to read data - table definition has changed
CHANGES
Datapump expdp is being used with the FLASHBACK_TIME or FLASHBACK_SCN options specified.
CAUSE
The issue is addressed in
Bug 9110642 - ORA-1466 using EXPDP with FLASHBACK_TIME option using SYSDATE
The issue may particularly arise when SYSDATE is being referenced for the FLASHBACK_TIME
The bug is fixed in
12.1.0.1 (Base Release)
11.2.0.3 (Server Patch Set)
Please refer to
Note 9110642.8 - Bug 9110642 - ORA-1466 using EXPDP with FLASHBACK_TIME option using SYSDATE
SOLUTION
To solve the issue, use any of below alternatives:
o Upgrade to 12c
- OR -
o Apply patch set 11.2.0.3 or higher
- OR -
o Apply interim Patch 9110642 if available for your platform and (PSU) patch level
To check for conflicting patches, please use the MOS Patch Planner Tool
Please refer to
Note 1317012.1 - How To Use MOS Patch Planner To Check And Request The Conflict Patches?
- OR -
o As a workaround
- Do not use the FLASHBACK_TIME or FLASHBACK_SCN options
- Use the original export/import.