这篇文章给大家分享的是有关oracle中出现ORA-00600内部错误怎么办的内容。小编觉得挺实用的，因此分享给大家做个参考，一起跟随小编过来看看吧。
ORA-00600: 内部错误代码, 参数: [kcbnew_3]
一：环境信息
DB：Oracle
11.2.0.3.0
OS：Windows
Server 2008
二：问题现象
portal前台报错：
警告日志：
Wed Nov 15 09:08:45 2017
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_6324.trc (incident=63384):
ORA-00600: 内部错误代码, 参数: [kcbnew_3],
[0], [76058], [4], [], [], [], [], [], [], [], []
Use ADRCI or Support Workbench to package
the incident.
See Note 411.1 at My Oracle Support for
error and packaging details.
跟踪日志orcl_ora_6324.trc：
DDE: Problem Key 'ORA 600 [kcbnew_3]' was
flood controlled (0x6) (incident: 63384)
ORA-00600: 内部错误代码, 参数:
[kcbnew_3], [0], [76058], [4], [], [], [], [], [], [], [], []
Dump of buffer cache at level 10 for tsn=6
rdba=29499424
BH (0x000000152FF4F868) file#: 7 rdba:
0x01c22020 (7/139296) class: 1 ba: 0x000000152EA10000
set: 78 pool: 3 bsz: 8192 bsi: 0 sflg: 1 pwc: 1646,28
dbwrid: 1 obj: 286891 objn: 286891 tsn: 6 afn: 7 hint: f
hash: [0x000000158F99A338,0x00000039D9FA7BA0] lru:
[0x000000152FF4FBB0,0x000000152FF4F820]
ckptq: [NULL] fileq: [NULL] objq:
[0x000000152FF4FBD8,0x000000152FF4F848] objaq:
[0x000000152FF4FBE8,0x000000152FF4F858]
st:
XCURRENT md: NULL fpin: 'kdswh21: kdst_fetch' tch: 1
flags: only_sequential_access
LRBA: [0x0.0.0] LSCN: [0x0.0] HSCN: [0xffff.ffffffff] HSUB: [65535]
buffer tsn: 6 rdba: 0x01c22020 (7/139296)
scn: 0x0000.0bc4eb5e seq: 0x01 flg: 0x06 tail: 0xeb5e0601
frmt: 0x02 chkval: 0x22e8 type: 0x06=trans data
......
三：解决方案
清空数据库缓存(正式环境需谨慎使用)
alter system flush buffer_cache;
ORA-600 [kcbnew_3] (文档 ID 204512.1)
| 转到底部 |
|
| 修改时间:
2017-10-26
类型:
REFERENCE
|
|
Note: For additional ORA-600 related
information please read PURPOSE:
it means and possible actions. The information here is only applicable You can restrict the list below to issues likely to affect one of the
following versions by clicking the relevant button:
indicates
that an alert exists for that issue. ·'+' Note:1944526.1<1span style="font-size:12pt;font-family:;" "=""> for details of other symbols used |
Bug 5218905 - OERI[kcbnew_3] when segment
advisor has been used (文档 ID 5218905.8)
| 转到底部 |
|
| 修改时间:
2012-7-26
类型:
PATCH
|
|
Bug 5218905 OERI[kcbnew_3] when
segment advisor has been used
This note gives a brief overview of
bug 5218905.
The content was last updated on: 03-APR-2009
Click here for details of each of the sections below.
Affects:
Product (Component)
Oracle Server (Rdbms)
Range of versions believed to be
affected
Versions < 11
Versions confirmed as being
affected
10.2.0.1
10.2.0.2
10.2.0.3
Platforms affected
Generic (all / most platforms affected) Fixed:
This issue is fixed in
10.2.0.3 Patch 28 on Windows Platforms
10.2.0.4 (Server Patch Set)
11.1.0.6 (Base Release)
Symptoms:
Related To:
Internal Error May Occur (ORA-600)
ORA-600 [kcbnew_3]
(None
Specified) Description
ORA-600 [kcbnew_3] can occur when segment
advisor has been running on an instance as it can
read blocks into the cache as CURRENT when it should
have read them as CR. Note: The presence of ORA-600 [kcbnew_3]
does not mean
that you HAVE encountered this problem as there can
be other reasons for a wrong block in the cache. Workaround
Do
not use segment advisor.
eg: connect / as sysdba;
exec dbms_scheduler.disable('AUTO_SPACE_ADVISOR_JOB');
Use "alter system flush buffer_cache" to clear bad blocks
from the cache Note:
Also see <Bug:4430244> Please note: The above is a summary description only. Actual symptoms can
vary. Matching to any symptoms here does not confirm that you are
encountering this problem. Always consult with Oracle Support for advice. References
Bug:5218905 (This link will only work for
PUBLISHED bugs)
Note:245840.1 Information on the sections in this article |
感谢各位的阅读！关于“oracle中出现ORA-00600内部错误怎么办”这篇文章就分享到这里了，希望以上内容可以对大家有一定的帮助，让大家可以学到更多知识，如果觉得文章不错，可以把它分享出去让更多的人看到吧！