ORA-7445 kgskhighthreshold Occurs After CPU Count Changed (Doc ID 805206.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]
Information in this document applies to any platform.
*** Checked for relevance on 17-Nov-2010 ***
*** Checked for relevance on 29-Aug-2013 ***


Symptoms

ORA-07445 kgskhighthreshold can occur when the CPU count is dynamically changed.

In alert.log:

Thu Mar 9 09:22:57 2009
Thread 1 advanced to log sequence 1988 (LGWR switch)
Current log# 2 seq# 1988 mem# 0: /oracle/test/redo02.log
Thu Mar 9 09:23:03 2009
Detected change in CPU count to 2
Thu Mar 9 09:23:03 2009
Errors in file /oracle/test/bdump/test_ckpt_7401.trc:
ORA-07445: exception encountered: core dump [kgskhighthreshold()+72] [SIGSEGV] [Address not mapped to object] [0x0000001F6] [] []
Thu Mar 9 09:23:13 2009
Errors in file /oracle/test/bdump/test_pmon_7376.trc:
ORA-00469: CKPT process terminated with error
Thu Mar 9 09:23:13 2009
PMON: terminating instance due to error 469
Instance terminated by PMON, pid = 7376

  


The trace file confirms a call stack similar to the following example:

kgskhighthreshold kskcpucc ksbcpu_mod kspptval kspset0 kspset ksbcpu_poll ...

  

Changes

CPU count changed dynamically. This is indicated by alert log file entry:

Detected change in CPU count to 'nn'

  

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms