使用expdp时报了一个ORA 600 错误

chiyiangel

在使用expdp导库时 每次导到

1. 处理对象类型 SCHEMA_EXPORT/SYSTEM_GRANT
   
2. 处理对象类型 SCHEMA_EXPORT/ROLE_GRANT
   
3. 处理对象类型 SCHEMA_EXPORT/DEFAULT_ROLE
   
4. 处理对象类型 SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
   
5. 处理对象类型 SCHEMA_EXPORT/TYPE/TYPE_SPEC
   
6. 处理对象类型 SCHEMA_EXPORT/DB_LINK
   
7. 处理对象类型 SCHEMA_EXPORT/SEQUENCE/SEQUENCE
   
8. 处理对象类型 SCHEMA_EXPORT/TABLE/TABLE
   
9. 处理对象类型 SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
   
10. ORA-39014: 一个或多个 worker 进程已过早地退出。
    
11. ORA-39029: worker 进程 1 (进程名为 "DW00") 过早地终止
    
12. ORA-31671: Worker 进程 DW00 有未处理的异常错误。
    
13. ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
    
14. ORA-06512: 在 "SYS.KUPW$WORKER", line 1751
    
15. ORA-06512: 在 line 2
    
16. 作业 "NC60_BIGDATA"."EXPDP" 因致命错误于 11:35:43 停止

复制代码

就报错


使用network link 进行倒库也是到
SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
这里出现的错误
日志

1. 处理对象类型 SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
   
2. ORA-39014: 一个或多个 worker 进程已过早地退出。
   
3. ORA-39029: worker 进程 1 (进程名为 "DW00") 过早地终止
   
4. ORA-31671: Worker 进程 DW00 有未处理的异常错误。
   
5. ORA-00600: 内部错误代码, 参数: [ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
   
6. ORA-06512: 在 "SYS.DBMS_METADATA", line 5466
   
7. ], [], [], [], [], [], [], [], [], [], [], []
   
8. ORA-02063: 紧接着 line (起自 BIGDATALINK)
   
9. ORA-06512: 在 "SYS.KUPW$WORKER", line 1751
   
10. ORA-06512: 在 line 2
    
11. 
    
12. ORA-39014: 一个或多个 worker 进程已过早地退出。
    
13. ORA-39029: worker 进程 9 (进程名为 "DW08") 过早地终止
    
14. ORA-31671: Worker 进程 DW08 有未处理的异常错误。
    
15. ORA-00600: 内部错误代码, 参数: [ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
    
16. ORA-06512: 在 "SYS.DBMS_METADATA", line 5466
    
17. ], [], [], [], [], [], [], [], [], [], [], []
    
18. ORA-02063: 紧接着 line (起自 BIGDATALINK)
    
19. ORA-06512: 在 "SYS.KUPW$WORKER", line 1751
    
20. ORA-06512: 在 line 2

复制代码

相关 alert_log 如下 其他相关 trace 打包发上来了 见附件

1. Thread 1 advanced to log sequence 73885 (LGWR switch)
   
2.   Current log# 4 seq# 73885 mem# 0: /opt/app/oradata/orcl/redo04.log
   
3. Sat Apr 28 19:34:00 2012
   
4. Thread 1 advanced to log sequence 73886 (LGWR switch)
   
5.   Current log# 5 seq# 73886 mem# 0: /opt/app/oradata/orcl/redo05.log
   
6. Sat Apr 28 19:36:48 2012
   
7. Suspending MMON slave action kewrmapsa_ for 82800 seconds
   
8. Sat Apr 28 19:40:52 2012
   
9. Thread 1 advanced to log sequence 73887 (LGWR switch)
   
10.   Current log# 6 seq# 73887 mem# 0: /opt/app/oradata/orcl/redo06.log
    
11. Sat Apr 28 19:50:37 2012
    
12. Thread 1 advanced to log sequence 73888 (LGWR switch)
    
13.   Current log# 4 seq# 73888 mem# 0: /opt/app/oradata/orcl/redo04.log
    
14. Sat Apr 28 20:01:35 2012
    
15. Thread 1 advanced to log sequence 73889 (LGWR switch)
    
16.   Current log# 5 seq# 73889 mem# 0: /opt/app/oradata/orcl/redo05.log
    
17. Sat Apr 28 20:13:41 2012
    
18. Thread 1 advanced to log sequence 73890 (LGWR switch)
    
19.   Current log# 6 seq# 73890 mem# 0: /opt/app/oradata/orcl/redo06.log
    
20. Sun Apr 29 14:00:00 2012
    
21. Closing scheduler window
    
22. Closing Resource Manager plan via scheduler window
    
23. Clearing Resource Manager plan via parameter
    
24. Sun Apr 29 18:00:00 2012
    
25. Setting Resource Manager plan SCHEDULER[0x310D]:DEFAULT_MAINTENANCE_PLAN via scheduler window
    
26. Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
    
27. Sun Apr 29 18:00:00 2012
    
28. Starting background process VKRM
    
29. Sun Apr 29 18:00:00 2012
    
30. VKRM started with pid=26, OS id=5550
    
31. Sun Apr 29 18:00:02 2012
    
32. Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
    
33. Sun Apr 29 18:06:23 2012
    
34. End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
    
35. Sun Apr 29 19:35:43 2012
    
36. Thread 1 advanced to log sequence 73891 (LGWR switch)
    
37.   Current log# 4 seq# 73891 mem# 0: /opt/app/oradata/orcl/redo04.log
    
38. Sun Apr 29 19:36:31 2012
    
39. Suspending MMON slave action kewrmapsa_ for 82800 seconds
    
40. Sun Apr 29 22:36:42 2012
    
41. XDB installed.
    
42. XDB initialized.
    
43. Mon Apr 30 06:33:57 2012
    
44. Errors in file /opt/app/diag/rdbms/orcl/orcl/trace/orcl_ora_2216.trc  (incident=408297):
    
45. ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
    
46. Incident details in: /opt/app/diag/rdbms/orcl/orcl/incident/incdir_408297/orcl_ora_2216_i408297.trc
    
47. Mon Apr 30 06:34:23 2012
    
48. Use ADRCI or Support Workbench to package the incident.
    
49. See Note 411.1 at My Oracle Support for error and packaging details.
    
50. Mon Apr 30 06:34:23 2012
    
51. Sweep [inc][408297]: completed
    
52. Sweep [inc2][408297]: completed
    
53. Mon Apr 30 06:34:23 2012
    
54. Dumping diagnostic data in directory=[cdmp_20120430063423], requested by (instance=1, osid=2216), summary=[incident=408297].
    
55. Mon Apr 30 06:47:02 2012
    
56. Errors in file /opt/app/diag/rdbms/orcl/orcl/trace/orcl_ora_448.trc  (incident=408313):
    
57. ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
    
58. Incident details in: /opt/app/diag/rdbms/orcl/orcl/incident/incdir_408313/orcl_ora_448_i408313.trc
    
59. Use ADRCI or Support Workbench to package the incident.
    
60. See Note 411.1 at My Oracle Support for error and packaging details.
    
61. Mon Apr 30 06:47:06 2012
    
62. Dumping diagnostic data in directory=[cdmp_20120430064706], requested by (instance=1, osid=448), summary=[incident=408313].
    
63. Mon Apr 30 06:47:06 2012
    
64. Sweep [inc][408313]: completed
    
65. Sweep [inc2][408313]: completed
    
66. Mon Apr 30 09:55:46 2012
    
67. DM00 started with pid=28, OS id=15146, job NC60_BIGDATA.EXPDP
    
68. Mon Apr 30 09:55:48 2012
    
69. DW00 started with pid=33, OS id=15156, wid=1, job NC60_BIGDATA.EXPDP
    
70. Mon Apr 30 09:56:48 2012
    
71. DW01 started with pid=31, OS id=15235, wid=2, job NC60_BIGDATA.EXPDP
    
72. Mon Apr 30 09:56:48 2012
    
73. DW02 started with pid=35, OS id=15237, wid=3, job NC60_BIGDATA.EXPDP
    
74. Mon Apr 30 09:56:48 2012
    
75. DW03 started with pid=36, OS id=15239, wid=4, job NC60_BIGDATA.EXPDP
    
76. Mon Apr 30 09:56:48 2012
    
77. DW04 started with pid=41, OS id=15241, wid=5, job NC60_BIGDATA.EXPDP
    
78. Mon Apr 30 09:56:48 2012
    
79. DW05 started with pid=42, OS id=15243, wid=6, job NC60_BIGDATA.EXPDP
    
80. Mon Apr 30 09:56:48 2012
    
81. DW06 started with pid=45, OS id=15245, wid=7, job NC60_BIGDATA.EXPDP
    
82. Mon Apr 30 09:56:48 2012
    
83. DW07 started with pid=46, OS id=15247, wid=8, job NC60_BIGDATA.EXPDP
    
84. Mon Apr 30 11:34:34 2012
    
85. Errors in file /opt/app/diag/rdbms/orcl/orcl/trace/orcl_dw00_15156.trc  (incident=408298):
    
86. ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
    
87. Incident details in: /opt/app/diag/rdbms/orcl/orcl/incident/incdir_408298/orcl_dw00_15156_i408298.trc
    
88. Mon Apr 30 11:35:03 2012
    
89. Use ADRCI or Support Workbench to package the incident.
    
90. See Note 411.1 at My Oracle Support for error and packaging details.
    
91. Mon Apr 30 11:35:03 2012
    
92. Sweep [inc][408298]: completed
    
93. Sweep [inc2][408298]: completed
    
94. Errors in file /opt/app/diag/rdbms/orcl/orcl/trace/orcl_dw00_15156.trc  (incident=408299):
    
95. ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
    
96. ORA-06512: 在 "SYS.KUPW$WORKER", line 1751
    
97. ORA-06512: 在 line 2
    
98. Incident details in: /opt/app/diag/rdbms/orcl/orcl/incident/incdir_408299/orcl_dw00_15156_i408299.trc
    
99. Mon Apr 30 11:35:04 2012
    
100. Dumping diagnostic data in directory=[cdmp_20120430113504], requested by (instance=1, osid=15156 (DW00)), summary=[incident=408298].
     
101. Use ADRCI or Support Workbench to package the incident.
     
102. See Note 411.1 at My Oracle Support for error and packaging details.
     
103. DW00 terminating with fatal err=600, pid=33, wid=1, job NC60_BIGDATA.
     
104. Dumping diagnostic data in directory=[cdmp_20120430113506], requested by (instance=1, osid=15156 (DW00)), summary=[incident=408299].
     
105. Mon Apr 30 11:35:41 2012
     
106. Errors in file /opt/app/diag/rdbms/orcl/orcl/trace/orcl_dm00_15146.trc  (incident=408257):
     
107. ORA-31671: Worker 进程 DW00 有未处理的异常错误。
     
108. ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
     
109. ORA-06512: 在 "SYS.KUPW$WORKER", line 1751
     
110. ORA-06512: 在 line 2
     
111. Incident details in: /opt/app/diag/rdbms/orcl/orcl/incident/incdir_408257/orcl_dm00_15146_i408257.trc
     
112. Use ADRCI or Support Workbench to package the incident.
     
113. See Note 411.1 at My Oracle Support for error and packaging details.
     
114. Mon Apr 30 11:35:43 2012
     
115. DW04 terminating with fatal err=31673, pid=41, wid=5, job NC60_BIGDATA.
     
116. Mon Apr 30 11:35:43 2012
     
117. DW02 terminating with fatal err=31673, pid=35, wid=3, job NC60_BIGDATA.
     
118. Mon Apr 30 11:35:43 2012
     
119. DW03 terminating with fatal err=31673, pid=36, wid=4, job NC60_BIGDATA.
     
120. Mon Apr 30 11:35:43 2012
     
121. DW05 terminating with fatal err=31673, pid=42, wid=6, job NC60_BIGDATA.
     
122. Mon Apr 30 11:35:43 2012
     
123. DW01 terminating with fatal err=31673, pid=31, wid=2, job NC60_BIGDATA.
     
124. Mon Apr 30 11:35:43 2012
     
125. DW07 terminating with fatal err=31673, pid=46, wid=8, job NC60_BIGDATA.
     
126. Mon Apr 30 11:35:43 2012
     
127. DW06 terminating with fatal err=31673, pid=45, wid=7, job NC60_BIGDATA.
     
128. Mon Apr 30 11:35:43 2012
     
129. Dumping diagnostic data in directory=[cdmp_20120430113543], requested by (instance=1, osid=15146 (DM00)), summary=[incident=408257].
     
130. Mon Apr 30 11:36:05 2012
     
131. Sweep [inc][408299]: completed
     
132. Sweep [inc][408257]: completed
     
133. Sweep [inc2][408299]: completed
     
134. Sweep [inc2][408257]: completed

复制代码

Kamus

EXCLUDE=GRANT 以后可以成功导出吗？

wqqzlm

Cause
This issue is due to Bug 10378005 and can report ORA-00600 [KOLRARFC: INVALID LOB TYPE] errors along with other datapump export errors

Maclean Liu(刘相兵

ODM DATA:

11.2.0.2 on Linux X86-64

Dump continued from file: /opt/app/diag/rdbms/orcl/orcl/trace/orcl_dw00_15156.trc
ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
ORA-06512: 在 "SYS.KUPW$WORKER", line 1751
ORA-06512: 在 line 2

========= Dump for incident 408299 (ORA 600 [ORA-00600: 内部错误代码, 参数: [kolrarfc: invalid lob type], [], [], [], [], [], [], [], [], [], [], []
ORA-06512: 在 ]) ========

*** 2012-04-30 11:35:03.932
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.


stack call

ksvrdp=> kupprwp => kuppChkErr= > 报错

KST　TRACE:
Trace Bucket Dump Begin: default bucket for process 33 (osid: 15156, DW00)
TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
-------------------------------------------------------------------------------
2012-04-30 11:34:12.884221*:87BA57FA:sql_mon_query:keswx.c@6326:keswxCurPushMonitoring(end): monitoring started for xsc=0x2b0650dcf570
2012-04-30 11:34:12.884221*:87BA57FB:sql_mon_query:keswx.c@6154:keswxCurPushMonitoring(begin): xsc=0x2b064fd64738 monCtx=0x2b0650d5ef38 estart=1335750948 eid=16777216 ctx=0x26437dfe8 cwh=0x2b064fd57648 cpu=2026692 buffg=1492 interb=0 r=0 rb=0 w=0 wb=0
2012-04-30 11:34:12.884221*:87BA57FC:sql_mon_query:keswx.c@6216:keswxCurPushMonitoring(): monitoring already started for xsc=0x2b064fd64738
2012-04-30 11:34:12.884221*:87BA57FD:sql_mon_query:keswx.c@3076:keswxCurPushPlanMonitoring(begin): xsc=0x2b064fd64738 ctx=0x26437dfe8 li#=0 pe=0x28f6e0828 incarnation=9956
2012-04-30 11:34:12.884221*:87BA57FE:sql_mon_query:keswx.c@3304:keswxCurPushPlanMonitoring(end): xsc=0x2b064fd64738 dis_mon=0
2012-04-30 11:34:12.884221*:87BA57FF:sql_mon_query:keswx.c@6326:keswxCurPushMonitoring(end): monitoring started for xsc=0x2b064fd64738
2012-04-30 11:34:14.904214*:87BA592F:sql_mon_query:keswx.c@6154:keswxCurPushMonitoring(begin): xsc=0x2b0650dcf570 monCtx=0x2b0654360160 estart=1335756190 eid=16777216 ctx=0x285c0ee98 cwh=0x2b064ff913e8 cpu=2003695 buffg=1492 interb=0 r=0 rb=0 w=0 wb=0
2012-04-30 11:34:14.904214*:87BA5930:sql_mon_query:keswx.c@6216:keswxCurPushMonitoring(): monitoring already started for xsc=0x2b0650dcf570
2012-04-30 11:34:14.904214*:87BA5931:sql_mon_query:keswx.c@3076:keswxCurPushPlanMonitoring(begin): xsc=0x2b0650dcf570 ctx=0x285c0ee98 li#=283 pe=0x2912c1248 incarnation=10024


TRACE DUMP的DATA中可以发现LOB:

Block header dump:  0x00405583
Object id on Block? Y
seg/obj: 0xe3  csc: 0x00.2b31a  itc: 3  flg: -  typ: 1 - DATA
     fsl: 0  fnx: 0x0 ver: 0x01

Itl           Xid                  Uba         Flag  Lck        Scn/Fsc
0x01   0x0001.017.00000075  0x00c03758.0018.34  --U-    1  fsc 0x0000.0002b345
0x02   0x0000.000.00000000  0x00000000.0000.00  ----    0  fsc 0x0000.00000000
0x03   0x0000.000.00000000  0x00000000.0000.00  C---    0  scn 0x0000.00000000
bdba: 0x00405583
data_block_dump,data header at 0xa168c074
===============
tsiz: 0x1f88
hsiz: 0x14
pbl: 0xa168c074
     76543210
flag=--------
ntab=1
nrow=1
frre=-1
fsbo=0x14
fseo=0x69
avsp=0x55
tosp=0x55
0xe:pti[0]        nrow=1        offs=0
0x12:pri[0]        offs=0x69
block_row_dump:
tab 0, row 0, @0x69
tl: 7967 fb: -----LP- lb: 0x1  cc: 1
col  0: [7961]

Maclean Liu(刘相兵

ODM DATA:


Export Datapump Fails With ORA-600 [Kolrarfc: Invalid Lob Type]

Applies to:
Oracle Server - Enterprise Edition - Version: 11.2.0.2 and later   [Release: 11.2 and later ]
Information in this document applies to any platform.
Symptoms
Datapump Export expdp fails due to ORA-600 internal error [kolrarfc: invalid lob type], []
Cause
This issue is most likely caused by Bug:10378005 ORA-600 [kolrarfc: invalid lob type] from LOB garbage collection
Description
ORA-600 [kolrarfc: invalid lob type] can occur during
LOB garbage collection routines due to a high internal pin count.

eg:
This can affect EXPDP and/or XML related SQL.

eg:
expdp may get an error of the form:
ORA-31671: Worker process DW00 had an unhandled exception.
ORA-600[kolrarfc: invalid lob type]
Solution
This issue is caused by Bug:10378005 ORA-600 [kolrarfc: invalid lob type] from LOB garbage collection
Description
ORA-600 [kolrarfc: invalid lob type] can occur during
LOB garbage collection routines due to a high internal pin count.

To fix this defect, you will need to:

-> Either Apply our 11.2.0.3 patch set

-> Or Apply One-off Patch:10378005 that may be available depending on your current release and operating system.


Oracle官方宣称 11.2.0.3 或 One-off Patch:10378005 修改了 该 bug， 但是实际 Bug 11723820: ORA-00600 [KOLRARFC: INVALID LOB TYPE] WITH PATCH 10378005 INSTALLED 存在已安装 One-off Patch:10378005 后问题仍重现的情况。


建议:

1. 升级到 11.2.0.3 + latest PSU
2. 尝试绕过相关的file#: 1 rdba: 0x00405583 (1/21891) class: 1 ba: 0xa168c000 相关的LOB对象，或者尝试修复这些对象
3. 尝试使用exp 而非expdp
4. 忽略该问题

chiyiangel

谢谢各位 我打上了 11.2.0.2.3 的 PSU 已经 fix 该bug 了
不过还有个问题是
是因为 schema 中 LOB相关的 对象有问题才导致的么 ？