My Oracle Support Banner

Repeated Entries of "kjgcr_StatCheckCPU: runq based load is high" Messages in LMHB Trace (Doc ID 2626082.1)

Last updated on JANUARY 06, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Following repeated entries logged in lmhb trace file causing trace log size increase and space usage.

<INSTANCE_NAME1>_lmhb_41885.trc inside <ORACLE_BASE>/diag/rdbms/<DB_NAME>/<INSTANCE_NAME1>/trace location:

*** 2017-05-12 13:21:09.564
kjgcr_StatCheckCPU: runq based load is high (192/146)

*** 2017-05-12 13:28:39.757
kjgcr_StatCheckCPU: runq based load is high (135/92)

*** 2017-05-12 13:28:41.715
kjgcr_StatCheckCPU: runq based load is high (135/92)

*** 2017-05-12 13:28:55.827
kjgcr_StatCheckCPU: runq based load is high (163/94)

*** 2017-05-12 13:28:57.778
kjgcr_StatCheckCPU: runq based load is high (163/94)

 

OS statistics through 'top' command indicates not much load average during the time. Patch for Bug 20076781 is already applied.

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.