今天使用expdp数据泵导出数据时报错了。[oracle@srccat dumpdp]$ expdp srcb/srcb directory=dumpdir dumpfile=srcb.20120221.dm
今天使用expdp数据泵导出数据时报错了。
[oracle@srccat dumpdp]$ expdp srcb/srcb directory=dumpdir dumpfile=srcb.20120221.dmp
export: release 10.2.0.4.0 - production on tuesday, 21 february, 2012 11:11:20
connected to: oracle database 10g enterprise edition release 10.2.0.4.0 - production
with the partitioning, olap, data mining and real application testing options
ora-39006: internal error
ora-39065: unexpected master process exception in dispatch
ora-01403: no data found
ora-39097: data pump job encountered unexpected error 100
虽然不像网上其他人碰到的还出现ora-00600的错误，但是照着网上的做法，重新生成一些 datapump api用到的视图问题就解决了：
可以参考一下metalink上的文章：
expdp fails with ora-600 [unable to load xdb library] [id 736049.1]
修改时间 23-jun-2010 类型 problem 状态 published
in this document
applies to: oracle server - enterprise edition - version: 10.2.0.1 to 10.2.0.5.0 - release: 10.2 to 10.2
symptomsthis article is written specifically for when data pump export (expdp) fails with the following ora-00600 error seen in the alert log and also reported from the export log :
ora-00600: internal error code, arguments: [unable to load xdb library], [], []
it may be that this article will solve for other situations where the error is seen but as the error
is quite general and can be see due to >1 reason there is no guarantee. if in doubt please
raise a sr to oracle support.
the following symptoms will be seen :-
a) expdp session/log will look something like :-
connected to: oracle database 10g enterprise edition release 10.2.0.3.0 - 64bit production
with the partitioning, olap and data mining options
starting xx.sys_export_schema_01: gsa/********
estimate in progress using blocks method...
processing object type schema_export/table/table_data
total estimation using blocks method: 11.16 gb
processing object type schema_export/user
processing object type schema_export/system_grant
processing object type schema_export/role_grant
processing object type schema_export/default_role
processing object type schema_export/tablespace_quota
processing object type schema_export/pre_schema/procact_schema
processing object type schema_export/sequence/sequence
ora-39014: one or more workers have prematurely exited.
ora-39029: worker 1 with process name dw01 prematurely terminated
ora-31671: worker process dw01 had an unhandled exception.
ora-00600: internal error code, arguments: [unable to load xdb library], [], []
ora-06512: at sys.kupw$worker, line 1342
ora-06512: at line 2
job xx.sys_export_schema_01 stopped due to fatal error at 11:03:15
b) the ora-00600 trace will contain the sql :-
select /*+rule*/ sys_xmlgen(value(ku$), xmlformat.createformat2('cluster_t',
'7')), ku$.obj_num ,ku$.schema_obj.name ,ku$.schema_obj.name ,'cluster' ,ku$.schema_obj.owner_name from sys.ku$_cluster_view ku$ where not (bitand (ku$.schema_obj.flags,16)=16) and ku$.schema_obj.owner_name=:schema1 and not exists (select 1 from sys.ku$noexp_tab a where a.obj_type='cluster' and a.name= ku$.schema_obj.name and a.schema=ku$.schema_obj.owner_name) and not exists (select 1 from sys.ku$noexp_tab a where a.obj_type='schema' and a.name=ku$.schema_obj.owner_name);
----- pl/sql call stack -----
object line object
handle number name
c0000000b9a60d98 1050 package body sys.dbms_metadata
c0000000b9a60d98 1256 package body sys.dbms_metadata
c0000000b9a60d98 1583 package body sys.dbms_metadata
c0000000b9a60d98 1891 package body sys.dbms_metadata
c0000000b9a60d98 4224 package body sys.dbms_metadata
c0000000b9ac55a0 2005 package body sys.kupw$worker
c0000000b9ac55a0 6854 package body sys.kupw$worker
c0000000b9ac55a0 1259 package body sys.kupw$worker
c0000000b0534cc0 2 anonymous block
c) ora-00600 trace file call stack will be similar to :-
kgerinv
d) environment variables have been reviewed against note 351650.1
but are considered to be valid.
causethe cause seems linked to some corrupted ku$ objects but how the database gets into this
position is unclear from the ora-600 trace.
solutionas the sysdba user, please run the following scripts :-