刚刚在遭遇一个bug.
客户打开一个数据库报错如下：
Mon Sep 23 14:31:08 2013
Completed: ALTER DATABASE OPEN
Mon Sep 23 14:31:17 2013
Errors in file /oracle/admin/dtvboss/bdump/dtvboss_smon_4157.trc:
ORA-00600: internal error code, arguments: [ktprhtnew6], [], [], [], [], [], [], []
Mon Sep 23 14:31:18 2013
Fatal internal error happened while SMON was doing active transaction recovery.
Mon Sep 23 14:31:18 2013
Errors in file /oracle/admin/dtvboss/bdump/dtvboss_smon_4157.trc:
ORA-00600: internal error code, arguments: [ktprhtnew6], [], [], [], [], [], [], []
SMON: terminating instance due to error 474
Instance terminated by SMON, pid = 4157
Mon Sep 23 14:35:03 2013
WARNING: inbound connection timed out (ORA-3136)
Mon Sep 23 14:37:44 2013
WARNING: inbound connection timed out (ORA-3136)
Mon Sep 23 14:38:55 2013
WARNING: inbound connection timed out (ORA-3136)
Mon Sep 23 14:41:03 2013
WARNING: inbound connection timed out (ORA-3136)
经过查询是bug ，官方如下解释：
ORA-00600: internal error code, arguments: [ktprhtnew6] is reported prior to instance crash in the alert log
Stack Trace resembles the following:
ksedst < - ksedmp <- ksfdmp <- kgerinv <- kgeasnmierr <- ktprhtnew <- ktprdoit <- ktprsched <- $cold_kturec <- kturax <- ktprbeg <- ktmmon <- ktmSmonMain <- ksbrdp <- opirip <- $cold_opidrv <- sou2o <- $cold_opimai_real <- main <- main_opd_entry Cause The issue was identified as Bug 8310931 ORA-600 [KTPRHTNEW6] LEADING TO DATABASE CRASH Solution - error occurs in SMON process - usually occurs when cpu count is high e.g. 125 physical and 256 logical [if multithreading] 2- If confirmed to be the issue, Bug 8310931 is fixed in 11.2, patches exist for 10.2.0.4. If no patch is found for your platform you may request a backport be created. References BUG:8310931 - ORA-600 [KTPRHTNEW6] LEADING TO DATABASE CRASH
把cpu_count改低就ok，小于125就ok.
