Listener process tnslsnr using high memory if large number of clsc_nnnn.log in client directory (Doc ID 2115402.1)

Last updated on APRIL 20, 2017

Applies to:

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

Symptoms

Listener process tnslsnr in 11.2.0.4 Grid Infrastructure using more memory on one node than on the other:

node1: 

F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME COMD
1401 S oracle 23356 1 2 154 20 e0000006766c2040 3894 e000000516d32240 Oct 27 ? 2244:08 /ora_crs/bin/tnslsnr LISTENER -inherit

From pmap: 6000000000000000 14.2M 14.2M PD rw- [data] <<---------!

 

node2:

1401 S oracle 7653 1 0 154 20 e0000006a4ea7680 25850 e000000436ff6080 12:56:50 ? 0:18 /ora_crs/bin/tnslsnr LISTENER -inherit

From pmap: 6000000000000000 101M 101M PD rw- [data] <<---------!

 

Other symptoms include listener start takes long time and agent may time out "clsn_agent::abort"

 

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