After increasing LOGGING_LEVEL > 5: *ASSERTION FAILURE*. File [clsLog.cpp] Line [406] Condition [false] error with oraagent (Doc ID 2171120.1)

Last updated on SEPTEMBER 04, 2016

Applies to:

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

Symptoms

1) "crsctl stat res -t" shows resource status UNKNOWN. Dependent resources fails to start automatically. 

ora.db1.service1.svc
      1        OFFLINE OFFLINE                                                   
      2        ONLINE  UNKNOWN      rac2

ora.db1.db
     1        ONLINE  UNKNOWN      rac1
     2        ONLINE  UNKNOWN      rac2

ora.db2.db
     1        ONLINE  ONLINE       rac1               Open                
     2        ONLINE  ONLINE       rac2               Open

ora.db3.db
     1        ONLINE  ONLINE       rac1               Open                
     2        ONLINE  ONLINE       rac2               Open


2) Clusterware restart doesn't help to fix UNKNOWN resource status.

 

3) Manual startup of the resource may work

Example :  In case of database resource, it can be started using SQLPLUS but SRVCTL fails and resource status remains UNKNOWN in "crsctl stat res -t"

 

4) oraagent logs shows *ASSERTION FAILURE* for clsLog.cpp file. In some cases, Agent might crash ( and restart ) trying to start / stop the resource in question.  

2016-07-11 06:49:44.500: [    AGFW][3365947712]{2:61584:2525} Agent received the message: AGENT_HB[Engine] ID 12293:56333
2016-07-11 06:49:54.322: [    AGFW][3365947712]{2:61584:8822} Agent received the message: RESOURCE_CLEAN[ora.db1.db 2 1] ID 4100:56341
2016-07-11 06:49:54.322: [    AGFW][3365947712]{2:61584:8822} Preparing CLEAN command for: ora.db1.db 2 1
2016-07-11 06:49:54.322: [    AGFW][3365947712]{2:61584:8822} ora.db1.db 2 1 state changed from: UNKNOWN to: CLEANING
2016-07-11 06:49:54.324: [   AGENT][3357542720]{2:61584:8822} {2:61584:8822} Created alert : (:CLSGEN00100:) :  *ASSERTION FAILURE*. File [clsLog.cpp] Line [406] Condition [false]  <-----------------------
2016-07-11 06:49:54.465: [   AGENT][4266942560] Logging level for Module: allcomp  0
2016-07-11 06:49:54.465: [   AGENT][4266942560] Logging level for Module: default  0

  

 

Changes

Logging level has been increased for the resource: 

$GI_HOME/bin/crsctl stat res ora.db1.db -p | grep LOGGING_LEVEL

LOGGING_LEVEL=9

  

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