连接到: 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 Tes
已导出 ZHS16GBK 字符集和 AL16UTF16 NCHAR 字符集
服务器使用 AL32UTF8 字符集 (可能的字符集转换)
正在导出簇定义
... (had truncated)
...
. 即将导出 anbob 的表通过常规路径...
. . 正在导出表 ANBOB_IMAG
EXP-00003: 未找到段 (0,0) 的存储定义
. . 正在导出表 ANBOB_ITEM导出了 16 行
. . 正在导出表 ANBOB_UNION导出了 4 行
. . 正在导出表 ANBOB_INDICATOR_LIMIT
EXP-00003: 未找到段 (0,0) 的存储定义
. . 正在导出表 ANBOB_CREDIT导出了 6 行
EXP-00003: no storage definition found for segment (0, 0)
. . 正在导出表 ANBOB_MODEL导出了 1 行
. . 正在导出表 ANBOB_FILE
EXP-00003: 未找到段 (0,0) 的存储定义
. . 正在导出表 ANBOB_FILE_DETAILS
EXP-00003: 未找到段 (0,0) 的存储定义
. . 正在导出表 ANBOB_DEF0000000004
[oracle@db231 ~]$ oerr exp 3
00003, 00000, "no storage definition found for segment(%lu, %lu)"
// *Cause: Export could not find the storage definitions for a cluster,
// index, or table.
// *Action: Record the accompanying messages and report this as an Export
// internal error to customer support.
Diagnosis:
We could not find a storage clause for the named segment.
- The arguments above are file and block, referred to here as
F and B
- First determine what the segment is:
select * from dba_segments
where HEADER_FILE = F
and HEADER_BLOCK = B;
- If it is an INDEX see Bug:231159
- If it is a TABLE it may be best to run this to find table SEGMENTS
whose segment owner differs from the OBJECT owner:
select o.owner#, o.name, o.type#, o.namespace, s.user#
from obj$ o, tab$ t, seg$ s
where o.obj#=t.obj#
and t.file#=s.file#
and t.block#=s.block#
and o.owner#!=s.user#
;
Any rows returned should be investigated.
Solution:
1) run this sql, if something not like 0 returns move those indexes, if 0 returns go to step 2
select count(*) from dba_indexes where owner<>table_owner;
2) Rerun the export and specify the parameter COMPRESS=Y (this is the default value for COMPRESS).
if the error still occurs,
3) Copy $ORACLE_HOME/rdbms/admin/catexp.sql to $ORACLE_HOME/rdbms/admin/catexp2.sql
add this line to $ORACLE_HOME/rdbms/admin/catexp2.sql:
"UNION ALL select * from sys.exu9tneb"
run
$ORACLE_HOME/rdbms/admin/catexp2.sql
if the error still occurs,
4) Upgrade your client version. Your version must be equal or higher than exp version of your target db.
5) Check those tables with exp error had created segment? if not? try to allocate the segments space manully using this sql:
alter table xx allocate extent
6) I recommend try to using expdp instend of exp
This case solution is following:
sys@anbob>@p segment_cre
NAME VALUE
---------------------------------------- ----------------------------------------
deferred_segment_creation FALSE
I guess those tables that to export error should be created before modifying parameters deferred_segment_creation=false. and the exp client version is 11.2.0.1 lower than target DB version 11.2.0.4. when I using above 5# way, to allocate the segment's extent, try to exp again, it is worked fine at all. the exp-3 error does not throw again.
References MOS note[443453.1]
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Tes
已导出 ZHS16GBK 字符集和 AL16UTF16 NCHAR 字符集
服务器使用 AL32UTF8 字符集 (可能的字符集转换)
正在导出簇定义
... (had truncated)
...
. 即将导出 anbob 的表通过常规路径...
. . 正在导出表 ANBOB_IMAG
EXP-00003: 未找到段 (0,0) 的存储定义
. . 正在导出表 ANBOB_ITEM导出了 16 行
. . 正在导出表 ANBOB_UNION导出了 4 行
. . 正在导出表 ANBOB_INDICATOR_LIMIT
EXP-00003: 未找到段 (0,0) 的存储定义
. . 正在导出表 ANBOB_CREDIT导出了 6 行
EXP-00003: no storage definition found for segment (0, 0)
. . 正在导出表 ANBOB_MODEL导出了 1 行
. . 正在导出表 ANBOB_FILE
EXP-00003: 未找到段 (0,0) 的存储定义
. . 正在导出表 ANBOB_FILE_DETAILS
EXP-00003: 未找到段 (0,0) 的存储定义
. . 正在导出表 ANBOB_DEF0000000004
[oracle@db231 ~]$ oerr exp 3
00003, 00000, "no storage definition found for segment(%lu, %lu)"
// *Cause: Export could not find the storage definitions for a cluster,
// index, or table.
// *Action: Record the accompanying messages and report this as an Export
// internal error to customer support.
Diagnosis:
We could not find a storage clause for the named segment.
- The arguments above are file and block, referred to here as
F and B
- First determine what the segment is:
select * from dba_segments
where HEADER_FILE = F
and HEADER_BLOCK = B;
- If it is an INDEX see Bug:231159
- If it is a TABLE it may be best to run this to find table SEGMENTS
whose segment owner differs from the OBJECT owner:
select o.owner#, o.name, o.type#, o.namespace, s.user#
from obj$ o, tab$ t, seg$ s
where o.obj#=t.obj#
and t.file#=s.file#
and t.block#=s.block#
and o.owner#!=s.user#
;
Any rows returned should be investigated.
Solution:
1) run this sql, if something not like 0 returns move those indexes, if 0 returns go to step 2
select count(*) from dba_indexes where owner<>table_owner;
2) Rerun the export and specify the parameter COMPRESS=Y (this is the default value for COMPRESS).
if the error still occurs,
3) Copy $ORACLE_HOME/rdbms/admin/catexp.sql to $ORACLE_HOME/rdbms/admin/catexp2.sql
add this line to $ORACLE_HOME/rdbms/admin/catexp2.sql:
"UNION ALL select * from sys.exu9tneb"
run
$ORACLE_HOME/rdbms/admin/catexp2.sql
if the error still occurs,
4) Upgrade your client version. Your version must be equal or higher than exp version of your target db.
5) Check those tables with exp error had created segment? if not? try to allocate the segments space manully using this sql:
alter table xx allocate extent
6) I recommend try to using expdp instend of exp
This case solution is following:
sys@anbob>@p segment_cre
NAME VALUE
---------------------------------------- ----------------------------------------
deferred_segment_creation FALSE
I guess those tables that to export error should be created before modifying parameters deferred_segment_creation=false. and the exp client version is 11.2.0.1 lower than target DB version 11.2.0.4. when I using above 5# way, to allocate the segment's extent, try to exp again, it is worked fine at all. the exp-3 error does not throw again.
References MOS note[443453.1]
「喜欢这篇文章,您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容,转载时必须标注文章的来源(墨天轮),文章链接,文章作者等基本信息,否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容,欢迎发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。
评论
相关阅读
Oracle DataGuard高可用性解决方案详解
孙莹
531次阅读
2025-03-26 23:27:33
Oracle RAC 一键安装翻车?手把手教你如何排错!
Lucifer三思而后行
501次阅读
2025-04-15 17:24:06
墨天轮个人数说知识点合集
JiekeXu
412次阅读
2025-04-01 15:56:03
XTTS跨版本迁移升级方案(11g to 19c RAC for Linux)
zwtian
411次阅读
2025-04-08 09:12:48
【纯干货】Oracle 19C RU 19.27 发布,如何快速升级和安装?
Lucifer三思而后行
393次阅读
2025-04-18 14:18:38
Oracle SQL 执行计划分析与优化指南
Digital Observer
392次阅读
2025-04-01 11:08:44
Oracle 19c RAC更换IP实战,运维必看!
szrsu
353次阅读
2025-04-08 23:57:08
Oracle数据库一键巡检并生成HTML结果,免费脚本速来下载!
陈举超
348次阅读
2025-04-20 10:07:02
oracle定时任务常用攻略
virvle
321次阅读
2025-03-25 16:05:19
3月“墨力原创作者计划”获奖名单公布
墨天轮编辑部
320次阅读
2025-04-15 14:48:05
热门文章
移除DataGuard Standby配置导致Primary启动失败
2023-08-17 21287浏览
使用dblink产生的”SELECT /*+ FULL(P) +*/ * FROM XXXXX P ” 解析
2023-06-20 20890浏览
Troubleshooting 'ORA-28041: Authentication protocol internal error' change password 12c R2 DB
2020-04-08 13637浏览
浅谈ORACLE免费数据库Oracle Database XE (Express Edition) 版
2018-10-31 7580浏览
High wait event ‘row cache mutex’ in 12cR2、19c
2020-08-14 5561浏览