My Oracle Support Banner

Entries with clsssinit and clsssterm Messages Flood Trace Logs in Standalone Non-ASM Database (Doc ID 2601897.1)

Last updated on AUGUST 27, 2020

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


It has been observed that every minute two traces are generated in the RDBMS trace folder causing the mount point to get filled up. It is standalone environment without ASM, still generating below traces:



Oracle Database 12c Enterprise Edition Release - 64bit Production
Build label:    RDBMS_12.
System name: Linux
Node name: hostname
Release: 2.6.32-754.18.2.el6.x86_64
Version: #1 SMP Thu Jul 25 17:15:34 EDT 2019
Machine: x86_64
Instance name: DBNAME
Redo thread mounted by this instance: 1
Oracle process number: 182
Unix process pid: 33987, image: oracle@hostname

*** 2019-10-08T09:31:01.858687+02:00
*** SESSION ID:(1190.28748) 2019-10-08T09:31:01.858715+02:00
*** CLIENT ID:() 2019-10-08T09:31:01.858719+02:00
*** SERVICE NAME:(DBNAME) 2019-10-08T09:31:01.858723+02:00
*** MODULE NAME:(prometheus_oracle_exporter-amd64@hostname) 2019-10-08T09:31:01.858727+02:00 >>>>>>>>>>>>>>>>>>>>>>
*** ACTION NAME:() 2019-10-08T09:31:01.858732+02:00
*** CLIENT DRIVER:() 2019-10-08T09:31:01.858735+02:00

2019-10-08 09:31:01.820 : [ CSSCLNT][ CSSCLNT]clsssterm: terminating context (0x7f4d27d0fc78)
kgxgncin: clsssinit: CLSS init failed with status 3
kgxgncin: clsssinit: return status 3 (0 SKGXN not av) from CLSS





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

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