ORA-600(kjbrchkpkeywait:timeout)和ORA-600(kclcls_8)错误

最新推荐文章于 2026-07-16 15:58:25 发布
转载 最新推荐文章于 2026-07-16 15:58:25 发布 · 550 阅读 · 0

在执行表空间的迁移操作后，RAC数据库出现了上面的错误。

 

 

在节点1也就是执行表空间迁移的节点上，alert文件中出现了大量的ORA-600(kjbrchkpkeywait:timeout)错误，同时还出现了ORA-7445(kjxmgmb_breq_header)以及ORA-603错误。

详细信息如下：

Thu Sep 17 14:47:40 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_27466.trc:
ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [791819], [792720], [61114], [], [], [], []
Thu Sep 17 14:47:41 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_27466.trc:
ORA-07445: exception encountered: core dump [kjxmgmb_breq_header()+136] [SIGSEGV] [Address not mapped to object] [0x000000004] [] []
ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [791819], [792720], [61114], [], [], [], []
Thu Sep 17 14:47:41 2009
Trace dumping is performing id=[cdmp_20090917144741]
Thu Sep 17 14:48:23 2009
Trace dumping is performing id=[cdmp_20090917144823]
Thu Sep 17 14:49:05 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_3484.trc:
ORA-00600: 内部错误代码, 参数: [kjbrchkpkeywait:timeout], [791819], [792805], [61114], [], [], [], []
Thu Sep 17 14:49:06 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_3484.trc:
ORA-00600: 内部错误代码, 参数: [600], [], [], [], [], [], [], []
Thu Sep 17 14:49:06 2009
Trace dumping is performing id=[cdmp_20090917144906]
Thu Sep 17 14:49:48 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_3484.trc:
ORA-00603: ORACLE 服务器会话因致命错误而终止
ORA-00600: 内部错误代码, 参数: [600], [], [], [], [], [], [], []
Thu Sep 17 14:49:48 2009
Trace dumping is performing id=[cdmp_20090917144948]
Thu Sep 17 14:50:29 2009
Trace dumping is performing id=[cdmp_20090917145029]
Thu Sep 17 14:59:16 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_5801.trc:
ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [791819], [793416], [61114], [], [], [], []
Thu Sep 17 14:59:17 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_5801.trc:
ORA-00600: internal error code, arguments: [600], [], [], [], [], [], [], []
Thu Sep 17 14:59:17 2009
Trace dumping is performing id=[cdmp_20090917145917]
Thu Sep 17 14:59:18 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_5801.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [600], [], [], [], [], [], [], []
Thu Sep 17 14:59:20 2009
Trace dumping is performing id=[cdmp_20090917145920]
Thu Sep 17 14:59:23 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_17753.trc:
ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [791819], [793423], [61114], [], [], [], []
Thu Sep 17 14:59:24 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_17753.trc:
ORA-07445: exception encountered: core dump [kjxmgmb_breq_header()+136] [SIGSEGV] [Address not mapped to object] [0x000000004] [] []
ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [791819], [793423], [61114], [], [], [], []
Thu Sep 17 14:59:24 2009
Trace dumping is performing id=[cdmp_20090917145924]
Thu Sep 17 14:59:35 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_20760.trc:
ORA-00600: internal error code, arguments: [kclcls_8], [], [], [], [], [], [], []
Thu Sep 17 15:00:19 2009
Trace dumping is performing id=[cdmp_20090917150019]
Thu Sep 17 15:00:20 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_23218.trc:
ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [791819], [793480], [61114], [], [], [], []
Thu Sep 17 15:00:21 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_23218.trc:
ORA-07445: exception encountered: core dump [kjxmgmb_breq_header()+136] [SIGSEGV] [Address not mapped to object] [0x000000004] [] []
ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [791819], [793480], [61114], [], [], [], []
.
.
.
Thu Sep 17 15:08:43 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_17033.trc:
ORA-07445: exception encountered: core dump [kjxmgmb_breq_header()+136] [SIGSEGV] [Address not mapped to object] [0x000000004] [] []
ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [791819], [793982], [61114], [], [], [], []
Thu Sep 17 15:09:21 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_7778.trc:
ORA-00600: 内部错误代码, 参数: [kjbrchkpkeywait:timeout], [793120], [794021], [139374], [], [], [], []
Thu Sep 17 15:09:23 2009
Trace dumping is performing id=[cdmp_20090917150923]
Thu Sep 17 15:09:23 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_7778.trc:
ORA-00600: 内部错误代码, 参数: [600], [], [], [], [], [], [], []
Thu Sep 17 15:09:25 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_7778.trc:
ORA-00603: ORACLE 服务器会话因致命错误而终止
ORA-00600: 内部错误代码, 参数: [600], [], [], [], [], [], [], []
Thu Sep 17 15:09:26 2009
Thread 1 advanced to log sequence 49
  Current log# 4 seq# 49 mem# 0: +MEMBER/tradedb/tradedb_redo1_4_1_1g
  Current log# 4 seq# 49 mem# 1: +MEMBER/tradedb/tradedb_redo1_4_2_1g
Thu Sep 17 15:09:26 2009
Trace dumping is performing id=[cdmp_20090917150926]
Thu Sep 17 15:09:28 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_1851.trc:
ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [791819], [794028], [61114], [], [], [], []
.
.
.
Thu Sep 17 15:18:25 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb1_ora_18739.trc:
ORA-00603: ORACLE 服务器会话因致命错误而终止
ORA-00600: 内部错误代码, 参数: [600], [], [], [], [], [], [], []

其中ORA-603的错误也是ORA-600错误所造成的：

SQL> exec dbms_stats.gather_schema_stats(user, cascade => true)
BEGIN dbms_stats.gather_schema_stats(user, cascade => true); END;

*
第 1 行出现错误:
ORA-00603: ORACLE 服务器会话因致命错误而终止

这是收集统计信息报错对应的trace文件信息：

bash-3.00$ more /data/oracle/admin/tradedb/udump/tradedb1_ora_7778.trc
/data/oracle/admin/tradedb/udump/tradedb1_ora_7778.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
ORACLE_HOME = /data/oracle/product/10.2/database
System name:    SunOS
Node name:      ser1
Release:        5.10
Version:        Generic_139555-08
Machine:        sun4u
Instance name: tradedb1
Redo thread mounted by this instance: 1
Oracle process number: 34
Unix process pid: 7778, image: oracle@ser1 (TNS V1-V3)

*** ACTION NAME:() 2009-09-17 14:51:45.397
*** MODULE NAME:(SQL*Plus) 2009-09-17 14:51:45.397
*** SERVICE NAME:(SYS$USERS) 2009-09-17 14:51:45.397
*** SESSION ID:(147.6274) 2009-09-17 14:51:45.397
*** 2009-09-17 14:51:45.397
Cleanout Start
Cleanout End
*** 2009-09-17 15:09:21.300
 GCS RESOURCE 50f3f92f0 hashq [51057d560,51fb74638] name[0x2d00b.170000] pkey 62260
   grant 50c8ba7b8 cvt 0 send 0,0 write 0,0@65535
   flag 0x0 mdrole 0x0 mode 0 scan 0 role LOCAL
   disk: 0x0103.0706ae1d write: 0x0000.00000000 cnt 0x0 hist 0x7d
   xid 0x0000.000.00000000 sid 0 pkwait 901s
   pkey 62260
   hv 32 [stat 0x0, 0->0, wm 32767, RMno 0, reminc 4, dom 0]
   kjga st 0x4, step 0.0.0, cinc 4, rmno 10, flags 0x0
   lb 0, hb 0, myb 14849, drmb 14849, apifrz 0
   GCS SHADOW 50c8ba7b8,2 sq[50f3f9310,50f3f9310] resp[50f3f92f0,0x2d00b.170000] pkey 62260
     grant 0 cvt 0 mdrole 0x20 st 0x40 GRANTQ rl LOCAL
     master 0 owner 1 sid 0 remote[526fcda58,3] hist 0xa6752557
     history 0x17.0x15.0x12.0x1d.0x26.0x2. cflag 0x0 sender 0 flags 0x0 replay# 0
     disk: 0x0000.00000000 write request: 0x0000.00000000
     pi scn: 0x0000.00000000
     msgseq 0x2 updseq 0x0 reqids[3,0,0] infop 0x0
*** 2009-09-17 15:09:21.300
ksedmp: internal or fatal error
ORA-00600: 内部错误代码, 参数: [kjbrchkpkeywait:timeout], [793120], [794021], [139374], [], [], [], []
Current SQL statement for this session:
select /*+ no_parallel(t) no_parallel_index(t) dbms_stats cursor_sharing_exact use_weak_name_resl dynamic_sampling(0) no_monitoring
*/ count(*),count("REMOTE_USER_CODE"),count(distinct "REMOTE_USER_CODE"),sum(sys_op_opnsize("REMOTE_USER_CODE")),substrb(dump(min(su
bstrb("REMOTE_USER_CODE",1,32)),16,0,32),1,120),substrb(dump(max(substrb("REMOTE_USER_CODE",1,32)),16,0,32),1,120),count("REMOTE_USE
R_PASS"),count(distinct "REMOTE_USER_PASS"),sum(sys_op_opnsize("REMOTE_USER_PASS")),substrb(dump(min(substrb("REMOTE_USER_PASS",1,32
)),16,0,32),1,120),substrb(dump(max(substrb("REMOTE_USER_PASS",1,32)),16,0,32),1,120),count("REMOTE_USER_BROWSER"),count(distinct "R
EMOTE_USER_BROWSER"),sum(sys_op_opnsize("REMOTE_USER_BROWSER")),substrb(dump(min(substrb("REMOTE_USER_BROWSER",1,32)),16,0,32),1,120
),substrb(dump(max(substrb("REMOTE_USER_BROWSER",1,32)),16,0,32),1,120),count("REMOTE_USER_OS"),count(distinct "REMOTE_USER_OS"),sum
(sys_op_opnsize("REMOTE_USER_OS")),substrb(dump(min(substrb("REMOTE_USER_OS",1,32)),16,0,32),1,120),substrb(dump(max(substrb("REMOTE
_USER_OS",1,32)),16,0,32),1,120),count("REMOTE_USER_IP"),count(distinct "REMOTE_USER_IP"),sum(sys_op_opnsize("REMOTE_USER_IP")),subs
trb(dump(min(substrb("REMOTE_USER_IP",1,32)),16,0,32),1,120),substrb(dump(max(substrb("REMOTE_USER_IP",1,32)),16,0,32),1,120),count(
"SERVER_FIRST_MENU"),count(distinct "SERVER_FIRST_MENU"),sum(sys_op_opnsize("SERVER_FIRST_MENU")),substrb(dump(min(substrb("SERVER_F
IRST_MENU",1,32)),16,0,32),1,120),substrb(dump(max(substrb("SERVER_FIRST_MENU",1,32)),16,0,32),1,120),count("SERVER_SECOND_MENU"),co
unt(distinct "SERVER_SECOND_MENU"),sum(sys_op_opnsize("SERVER_SECOND_MENU")),substrb(dump(min(substrb("SERVER_SECOND_MENU",1,32)),16
,0,32),1,120),substrb(dump(max(substrb("SERVER_SECOND_MENU",1,32)),16,0,32),1,120),count("SERVER_HANDLER"),count(distinct "SERVER_HA
NDLER"),sum(sys_op_opnsize("SERVER_HANDLER")),substrb(dump(min(substrb("SERVER_HANDLER",1,32)),16,0,32),1,120),substrb(dump(max(subs
trb("SERVER_HANDLER",1,32)),16,0,32),1,120),count("SERVER_OPERATE"),count(distinct "SERVER_OPERATE"),sum(sys_op_opnsize("SERVER_OPER
ATE")),substrb(dump(min(substrb("SERVER_OPERATE",1,32)),16,0,32),1,120),substrb(dump(max(substrb("SERVER_OPERATE",1,32)),16,0,32),1,
120),count("SERVER_ERROR_MSG"),count(distinct "SERVER_ERROR_MSG"),sum(sys_op_opnsize("SERVER_ERROR_MSG")),substrb(dump(min(substrb("
SERVER_ERROR_MSG",1,32)),16,0,32),1,120),substrb(dump(max(substrb("SERVER_ERROR_MSG",1,32)),16,0,32),1,120),count("WEB_EXPEND_TIME")
,count(distinct "WEB_EXPEND_TIME"),sum(sys_op_opnsize("WEB_EXPEND_TIME")),substrb(dump(min("WEB_EXPEND_TIME"),16,0,32),1,120),substr
b(dump(max("WEB_EXPEND_TIME"),16,0,32),1,120),count(distinct "ERROR_CREATE_DATE"),substrb(dump(min("ERROR_CREATE_DATE"),16,0,32),1,1
20),substrb(dump(max("ERROR_CREATE_DATE"),16,0,32),1,120),sum(sys_op_opnsize("ID")),substrb(dump(min("ID"),16,0,32),1,120),substrb(d
ump(max("ID"),16,0,32),1,120) from "ZHEJIANG"."EMED_WEB_LOG" sample (   .4800581069) t  where TBL$OR$IDX$PART$NUM("ZHEJIANG"."EMED_W
EB_LOG",0,4,0,"ROWID") = :objn
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
52083e9d0      1218  package body SYS.DBMS_SYS_SQL
52083ef30       334  package body SYS.DBMS_SQL
520974208     10750  package body SYS.DBMS_STATS
520974208     12215  package body SYS.DBMS_STATS
520974208     12494  package body SYS.DBMS_STATS
520974208     12623  package body SYS.DBMS_STATS
520974208     13090  package body SYS.DBMS_STATS
520974208     13291  package body SYS.DBMS_STATS
520974208     13682  package body SYS.DBMS_STATS
520974208     13760  package body SYS.DBMS_STATS
520974208     13719  package body SYS.DBMS_STATS
4d271a018         1  anonymous block
----- Call Stack Trace -----
calling              call     entry                argument values in hex     
location             type     point                (? means dubious value)    
-------------------- -------- -------------------- ----------------------------
ksedmp()+744         CALL     ksedst()             000000840 ?
                                                   FFFFFFFF7FFEF34C ?
                                                   000000000 ?
                                                   FFFFFFFF7FFEBE40 ?
                                                   FFFFFFFF7FFEABA8 ?
                                                   FFFFFFFF7FFEB5A8 ?
kgerinv()+200        PTR_CALL 0000000000000000     000106400 ? 10652D264 ?
                                                   10652D000 ? 00010652D ?
                                                   000106400 ? 10652D264 ?
kgeasnmierr()+28     CALL     kgerinv()            106527C18 ? 000000000 ?
                                                   105FFA068 ? 000000003 ?
                                                   FFFFFFFF7FFEF7F0 ?
                                                   000001430 ?
kjbcropen()+4892     CALL     kgeasnmierr()        106527C18 ?
                                                   FFFFFFFF7C026270 ?
                                                   105FFA068 ? 000000003 ?
                                                   000000000 ? 0000C1A20 ?
kclscrs()+1200       CALL     kjbcropen()          10652D000 ? 1065278D8 ?
                                                   000106400 ? 105FFA000 ?
                                                   000106400 ? 0000C1DA5 ?
kclgclk()+9936       CALL     kclscrs()            000000000 ? 000004000 ?
                                                   000000000 ?
                                                   FFFFFFFF7FFEFBB0 ?
                                                   000000000 ? 000000000 ?

而在另外一个节点，则错误主要以ORA-600()为主：

Thu Sep 17 14:50:10 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb2_ora_18519.trc:
ORA-00600: internal error code, arguments: [kclcls_8], [], [], [], [], [], [], []
Thu Sep 17 14:50:46 2009
Trace dumping is performing id=[cdmp_20090917145046]
Thu Sep 17 14:52:21 2009
Trace dumping is performing id=[cdmp_20090917144741]
Thu Sep 17 14:53:03 2009
Trace dumping is performing id=[cdmp_20090917144823]
Thu Sep 17 14:53:46 2009
Trace dumping is performing id=[cdmp_20090917144906]
Thu Sep 17 14:54:28 2009
Trace dumping is performing id=[cdmp_20090917144948]
Thu Sep 17 14:55:09 2009
Trace dumping is performing id=[cdmp_20090917145029]
Thu Sep 17 15:03:57 2009
Trace dumping is performing id=[cdmp_20090917145917]
Thu Sep 17 15:04:00 2009
Trace dumping is performing id=[cdmp_20090917145920]
Thu Sep 17 15:04:04 2009
Trace dumping is performing id=[cdmp_20090917145924]
Thu Sep 17 15:04:59 2009
Trace dumping is performing id=[cdmp_20090917150019]
Thu Sep 17 15:05:01 2009
Trace dumping is performing id=[cdmp_20090917150021]
Thu Sep 17 15:05:54 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb2_ora_20097.trc:
ORA-00600: internal error code, arguments: [kclcls_8], [], [], [], [], [], [], []
Thu Sep 17 15:05:56 2009
Trace dumping is performing id=[cdmp_20090917150556]
Thu Sep 17 15:05:58 2009
Trace dumping is performing id=[cdmp_20090917150118]
.
.
.
Thu Sep 17 15:51:16 2009
Errors in file /data/oracle/admin/tradedb/udump/tradedb2_ora_25090.trc:
ORA-00600: 内部错误代码, 参数: [kclcls_8], [], [], [], [], [], [], []

查询metalink，发现bug描述Doc ID:  5165885.8。虽然在这个bug中，并没有说明是什么导致了这个问题的产生，但是环境和现象的描述都与当前完全一致。这个bug影响10.2.0.3，也就是当前的版本。虽然Oracle提供了单独的补丁集，但是似乎安装这个补丁后有可能导致其他的ORA-600错误的产生，甚至是系统CRASH。

虽然Oracle没有说明是什么导致了问题，但是根据执行的操作可以推断出大致是什么原因。由于在执行迁移表空间的过程中，只是删除了表空间，而没有删除用户，因此应用程序并没有断开连接。由于RAC的特殊性，导致两个节点之间在处理不正确的CURSOR出现了问题，最终造成了两个节点的状态不一致，产生了大量的ORA-600错误。

重启整个数据库后，这个错误不再出现。

 

 

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

转载于:http://blog.itpub.net/4227/viewspace-614937/

标签
#数据库
rac异常hang死故障分析（sskgxpsnd2）
q195136130的专栏
09-04 1169
rac异常hang死记录
Oracle ASM警告日志错误ORA-00603:ORA-27504: ORA-27300:ORA-27301: ORA-27302:处理
wulinpingailxr的博客
05-06 4341
1.监控告警主机ASM磁盘错误： Fri May 03 08:01:01 2019 skgxpvfynet: mtype: 61 process 60277 failed because of a resource problem in the OS. The OS has most likely run out of buffers (rval: 4) Errors in file /orac...
@@@客户***数据库ORA-600 kjbrchkpkeyait问题分析总结
cuidong1521的博客
09-05 239
关键字：ORA-600 kjbrchkpkeyait作者：paulyibinyi一、问题描述：数据库版本：Oracle10.2.0.3 RAC操作系统版本：AIX2010-10-2下午13点多开始，***数据库文件系统节点1产生...
基于AI Agent的数据治理实战：从架构设计到企业级落地
最新发布
weixin_34008805的博客
07-16 403
数据治理是确保企业数据质量、一致性与安全性的核心实践，其核心原理在于通过规范、流程与技术工具对数据进行全生命周期管理。传统人工治理模式效率低下且难以规模化，而大语言模型（LLM）与智能体（Agent）技术的发展，为数据治理的自动化与智能化带来了突破。通过将自然语言理解、任务规划与工具调用能力相结合，AI Agent能够将治理规则“代码化”与“智能化”，实现从被动响应到主动发现的模式转变。在应用场景上，AI Agent可扮演智能数据专员角色，自动执行元数据问答、数据质量探查、口径对齐等任务，显著提升数据团队效
客户遭遇ORA-600 [Kjbrchkpkeywait:Timeout]引起实例down
cucanqi9387的博客
10-09 295
今天帮客户分析数据库down机问题，环境oracle 10.2.0.3 rac + aix 2节点 down机问题主要原因是：数据库后台日志不断报ORA-600 [kjbrchkpkeywai...
oracle ora-27544,ORA-603,ORA-27544 问题原因讨论
weixin_33739480的博客
04-03 455
ORA-603,ORA-27544 问题求助版本：ORACLE9207架构：ORACLE RAC + DATA GUARDOS: HPUX 11.23cluster:HP Service Guard A.11.17出现错误时，告警日志文件报错如下：Wed Dec 13 14:42:28 2006ARC0: Evaluating archive log 3 thread 1 sequence 2...
ora-603 ora-27504
lqkitten的专栏
07-08 2682
<br />linux as4 oracle9i 9206rac ,一台服务器因硬件原因宕机,另外一台开始时可以用java程序应用,用oem或sqlplus.plsql连接时报ora-00603,sqlplus / as sysdba,系统未启动,启动时报ora-00603,ora-27504错误.ifconfig lo,mtu=16386,修改ifconfig lo mtu 1500,再启动是,报ora-603,无其他提示.再看用于互联的eth1,并未UP,原来是两个节点,没有连接到交换机,用互联线连接,
ora12700linux,苏大文正 ORA-00603 ORA-27504 ORA-27300 ORA-27301 ORA-27302 BUG
weixin_28833069的博客
05-25 340
Problem Description---------------------------------------------------Tue Sep 01 04:05:33 2020skgxpvfynet: mtype: 61 process 417356 failed because of a resource problem in the OS. The OS has most like...
Oracle Linux网卡参数默认设置导致ORA-603
大叶梧桐的博客
08-29 1775
ORA-603，双节点RAC 节点2 alert日志报错
Oracle 19c 报ORA-704 ORA-01555故障处理---惜分飞
07-30 1175
异常断电导致数据库无法启动,尝试对数据文件进行recover操作,报ORA-00283 ORA-00742 ORA-00312错误,由于redo写丢失无法正常应用。屏蔽数据一致性,尝试强制打开库,报ORA-00604,ORA-00704,ORA-01555错误。alert日志对应错误。
ORA错误记录
rgb_rgb的博客
09-08 1697
2012-9-7 10:43:03： Errors in file /oracle/diag/rdbms/sgerp5/sgerp5/trace/sgerp5_ora_21692692.trc  (incident=842436): ORA-00600: 内部错误代码, 参数: [kdoirp-1], [2], [], [], [], [], [], [] Incident details
ORA-600 [kjbrchkpkeywait:timeout]
cuilonggui7816的博客
10-30 292
一大早接到报障，后台发现出现很多ORA-600 [kjbrchkpkeywait:timeout] 错误，该错误由insert插入分区表的sql引起。MOS上很多关于该类错误属于BUG的解析。Note: For addition...
ORA-600(4415)错误
ckawt40802的专栏
09-16 268
客户的11.2的DATA GUARD数据库出现了这个错误。 一般DATA GUARD数据库出现错误的可能性不大，而ORA-600错误的可能性就更小了，而且一旦出现，多...
ora-600 kclcls_8问题处理
枫树林
06-11 783
2013 年6月9号 周末 dbms: oracle11.1.0.7   4nodes RAC 报系统运行变的极度缓慢 查看系统等待事件,积压了很多的类如下语句 查看第一个节点的 insert into counterloadmessage(emsid,emsentityid,equipmentid,moentityid,startday,starttime,period,indicat
ORA-00600错误分析
congyuping9537的博客
12-07 541
ORA-00600错误分析[@more@]ORA-600大全http://dco-proxima.dco.pima.edu/oracle/bug/index/pr000512.htmORA-600错误1->解决思路ORA-...
oracle1
thy822的专栏
06-29 2244
个人BLOG文章索引09年马上要结束了，BLOG每天更新又坚持了一年，目前文章总数1700多篇，其中纯技术文章将近1300篇。我比较喜欢的一句话：十年磨一剑。以前提到过，坚持10年可能会比较困难，那么至少要坚持5年，到目前为止，BLOG更新已经4年了，明年就会初步实现目标了。重新整理一下BLOG上面文章的索引，把09年的文章放进去了，且重新整理了一下分类。 RAC方面：Redhat AS4
ORA-00603 解决方法
热门推荐
Cavenaghi 的专栏
05-18 2万+
     今天发现在使用OracleConnection连接ORACLE数据库的过程中突然出现连接不上的情况，dotNetFramework返回ORA-00603错误。     ORA-00603: ORACLE 服务器会话因致命错误而终止。     然后跟踪到trace日志。发现如下异常。         ksedmp: internal or fatal error ORA
oracle ora00569,ASM MANAGED DATABASE HITS ORA-00600 [ORA_NPI_ERROR], [603] + ORA-00569:
weixin_28836507的博客
04-07 429
APPLIES TO:Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterInformation in this document applies to any platform.SYMPTOMSThe following symptoms are known to be attributed to this issue...
ORA-00600 [4194]的解决
xionglang7的专栏
05-09 5143
今天遇到一个standby 拷贝出来的库要
azure云 ORA-00600: internal error code, arguments问题解决
csdn's blog
07-16 1万+
1，alert日志报错如下 Tue Feb 23 09:43:37 2016 Errors in file /oracle/app/oracle/diag/rdbms/powerdes/powerdes/trace/powerdes_dbw0_49724.trc (incident=87281): ORA-00600: internal error code, arguments: [1433]...
ora-00600: 内部错误代码, 参数: [4415], [], [], [], [], [], [], [], [], [], [], []
冰刀(skate)
12-01 1万+
author：skate time：2011/12/01   环境： os：CentOS release 5.5 db: 11.2.0.2.0 - 64bit Production physical dataguard   现象：只是报ora-00600: 内部错误代码, 参数: [4415]；数据库还是可以正常提供服务   诊断： 这套oracle11g的DG已经运行
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值