ORA-00600(unable to load XDB library)错误一例

目的：通过网络方式impdp：
源数据库，138，版本10.2.0.5，AIX
目标库，251，版本11.2.0.3，AIX

操作：
impdp bnet/bnet schemas=bnet303 transform=segment_attributes:n parallel=8 DIRECTORY=DMP_DIR logfile=imp_data_from_20138.log network_link=db_sit138 remap_schema=bnet303:bnet

结果报错，参考附件1：
ORA-00600: internal error code, arguments: [unable to load XDB library], [], [], [], [], [], [], [], [], [], [], []

解决方案，参考附件2和附件3：

在138上执行了：
alter system set event='10298 trace name context forever, level 32' scope = spfile;

在251上执行了：
As the SYSDBA user, please run the following scripts:
SQL>@/rdbms/admin/catmeta.sql
SQL>@/rdbms/admin/catmet2.sql
SQL>@/rdbms/admin/utlrp.sql

问题解决。

 

 

附件1：
Import: Release 11.2.0.3.0 - Production on Thu Apr 25 04:23:47 2013

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
Starting "bnet"."SYS_IMPORT_SCHEMA_01":  bnet/******** schemas=bnet303 transform=segment_attributes:n parallel=8 DIRECTORY=DMP_DIR logfile=imp_data_from_20138.log network_link=db_sit138 remap_schema=bnet303:bnet
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 196.7 GB
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"bnet" already exists
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/DB_LINK
ORA-31684: Object type DB_LINK:"bnet"."DB_DEV95" already exists
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
. . imported "bnet"."USERS"                           87966169 rows
. . imported "bnet"."TRANS_PER"                       25593424 rows
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 8 with process name "DW07" prematurely terminated
ORA-31671: Worker process DW07 had an unhandled exception.
ORA-00600: internal error code, arguments: [unable to load XDB library], [], [], [], [], [], [], [], [], [], [], []
ORA-01403: no data found
ORA-06512: at "SYS.KUPW$WORKER", line 1838
ORA-06512: at line 2

ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 9 with process name "DW07" prematurely terminated
ORA-31671: Worker process DW07 had an unhandled exception.
ORA-00600: internal error code, arguments: [unable to load XDB library], [], [], [], [], [], [], [], [], [], [], []
ORA-01403: no data found
ORA-06512: at "SYS.KUPW$WORKER", line 1838
ORA-06512: at line 2

Job "bnet"."SYS_IMPORT_SCHEMA_01" stopped due to fatal error at 04:55:19

 

附件2，
http://www.eygle.com/archives/2011/04/ora-00600_libxdb.html

在AIX环境中，如果环境变量设置顺序存在问题，可能会导致数据库运行出错，正常情况下LIBPATH的lib路径应当在lib32之前：
export LIBPATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib32

如果位置颠倒，则会出现类似如下错误：

ERROR
ORA-00600: internal error code, arguments: [unable to load XDB library]

----- Call Stack Trace -----
ksedst qmxtgrCheckMkXML
kxsGetRuntimeLock

或者:

Dynamic link error:    
0509-022 Cannot load module /app/oracle/product/10.2.0.3/db/lib32/libxdb.so.           
0509-103   The module has an invalid magic number.   

ksedmp: internal or fatal error   
ORA-600: internal error code, arguments: [unable to load XDB library], [], [], [], [], [], [], []   
Current SQL statement for this session:   
SELECT DBMS_XDB.CheckPrivileges( '/xdbconfig.xml', XMLType( '') )   
FROM DUAL   
----- PL/SQL Call Stack -----     
object      line  object      handle    number  name   
7000001255fab08       301  SYS.XMLTYPE   
70000010b5f8a20         1  anonymous block

修改环境变量，重新启动可以消除这个错误。

参考MOS： 759401.1

 

附件3，
EXPDP FAILS WITH ORA-600 [UNABLE TO LOAD XDB LIBRARY] (Doc ID 736049.1)

 Modified Date LabelModifiedModified Date23-JUN-2010Document Type LabelTypeDocument TypePROBLEMStatusPUBLISHED(EXTERNAL)Priority3To Bottom
In this Document
Symptoms
Cause
Solution
References

--------------------------------------------------------------------------------
Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.5.0 - Release: 10.2 to 10.2 Symptoms This 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     but are considered to be valid. Cause The cause seems linked to some corrupted KU$ objects but how the database gets into this
position is unclear from the ORA-600 trace. Solution
As the SYSDBA user, please run the following scripts :-

SQL>@/rdbms/admin/catmeta.sql
SQL>@/rdbms/admin/catmet2.sql
SQL>@/rdbms/admin/utlrp.sql

Then reattempt the running of EXPDP
This article is created based on observations and actions of two notes : Note 452289.1
and
Note 453796.1

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/18922393/viewspace-759282/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/18922393/viewspace-759282/