问题 : ORA-1400 During Import of Export Dump Written in Direct Path Mode

转载 2012年03月23日 17:09:14
connect test/test

drop table a_tab purge;

#> imp test/test file=a_tab.dmp tables=a_tab

Import: Release 11.1.0.7.0 - Production on Mon May 18 17:19:21 2009

Copyright (c) 1982, 2007, Oracle. All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Export file created by EXPORT:V11.01.00 via direct path
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. importing TEST's objects into TEST
. importing TEST's objects into TEST
. . importing table "A_TAB"
IMP-00019: row rejected due to ORACLE error 1400
IMP-00003: ORACLE error 1400 encountered
ORA-01400: cannot insert NULL into ("TEST"."A_TAB"."COL001")
Column : 1
Column :
IMP-00019: row rejected due to ORACLE error 1400
IMP-00003: ORACLE error 1400 encountered
ORA-01400: cannot insert NULL into ("TEST"."A_TAB"."COL001")
Column : 2
Column : 0 rows imported
Import terminated successfully with warnings.

Cause

The root cause of this behavior is the new feature introduced with 11gR1:

- the columns with property 1073741824 (see the column value PROPERTY in COL$ for column COL001) are columns with defaults that are not saved in the column. This means on disk, the null values for this column must be replaced by its default obtained from the column definition:

connect / as sysdba
select col#, name, property
from   col$
where  obj# in (select object_id
                from   dba_objects
                where  owner = 'TEST' and
                       object_name = 'A_TAB');

COL#       NAME                           PROPERTY
---------- ------------------------------ ----------
         1 ID                                      0
         2 COL001                         1073741824

2 rows selected.

This mechanism doesn't work properly when direct path is used with original export (the value is not replaced by its default but the NULL values is stored in export dump. This will produce ORA-1400 during import).

Original export (exp)is desupported in 11g so there is no opened bug against this product.

Solution

1. Use DataPump export/import utilities (expdp/impdp)

or:

2. Start traditional export utility (exp) in conventional path mode (DIRECT=N).


如下重新导出:

exp system/oracle@IODAC file=DEV_IODAC_`date +"%Y%m%d%H%M%S"`.dmp log=DEV_IODAC_`date +"%Y%m%d%H%M%S"`.log buffer=40960000 direct=N recordlength=65535 consistent=y full=y

再导入就不再出现错误了
举报

相关文章推荐

Study note about bulk import and export data in MSSQL

An XML native Format file This format file was created by using the following bcp command. cmd>bcp ...

An implementation of the skip list data structure written in C++

/* The authors of this work have released all rights to it and placed it in the public domain under...

我是如何成为一名python大咖的?

人生苦短,都说必须python,那么我分享下我是如何从小白成为Python资深开发者的吧。2014年我大学刚毕业..

"Optimization of AC Control in Hybrid Electric Vehicles during Urban Drive Conditions"笔记

第一篇博客,记录下今晚看的文献。 论文链接地址点击打开链接 1,摘要:这篇文献,是针对混合动力汽车的空调压缩机在不同城市工况下的控制策略。是建立在车速,坡度,SOC,空转起停和挡位的基础上。文中指...

ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

今天在发出全备份命令rman>backup database 时出现了以上错误 Cause: You tried to copy or backup a file that was not clos...

Oracle ORA-01102故障: cannot mount database in EXCLUSIVE mode

SQL> conn /as sysdba Connected to an idle instance. SQL> startup oracle instance started. Tota...

错误 ORA-01102: cannot mount database in EXCLUSIVE mode 的处理方法

今天启动数据库时报错了! SQL> startup mount         ORACLE instance started.   Total System Global A.....

ORA-01102: cannot mount database in EXCLUSIVE mode

ORA-01102: cannot mount database in EXCLUSIVE mode场景再现:SQL> startupORACLE instance started.Total Sys...

ORA-01102: cannot mount database in EXCLUSIVE mode

ORA-01102: cannot mount database in EXCLUSIVE mode 今天启动数据库时报错了! SQL> startup mount         ORAC...
返回顶部
收藏助手
不良信息举报
您举报文章:深度学习:神经网络中的前向传播和反向传播算法推导
举报原因:
原因补充:

(最多只允许输入30个字)