Skip to Main Content

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, NISHANTH.

Asked: June 26, 2018 - 6:40 am UTC

Last updated: April 12, 2019 - 2:20 am UTC

Version: oracle 12c

Viewed 1000+ times

You Asked

hi,

please help me to block the particular user entries in the Listener log file.because the size of file was increasing unexceptionally.

that user is frequently accessing the db server.i dont want to log the entries for that particular user.

For Example, every mins

it ll take around 60 entries in the listener log.



Note:

its a windows environment.The Listener log file size was increasing gradually more than expected due to multiple log entries.

please give me any suggestions for to control growth of the listener log file or how to block the user entry.




and Connor said...

I don't know of any means to block a particular connection attempt from the listener logs.

To keep the listener log under manageable size, you can truncate at regular intervals, eg

lsnrctl 
set current_listener temporary_name.log
set log_status off
 
mv listener.log listener.log.[datestamp]
 
lsnrctl 
set current_listener listener.log
set log_status on


If you're on unix, you could look at using 'logrotate' to manage this as well.

https://linux.die.net/man/8/logrotate

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

mv listener.log ?

Mike, April 11, 2019 - 7:09 pm UTC

I had a 3.2G listener.log file in a 12.1 environment, and mv of the listener.log file behaved the same as mv would to the alert log.

Has Oracle recently changed the listener to open/write/close in the same way as the alert log?
Connor McDonald
April 12, 2019 - 2:20 am UTC

I'm unaware of such an enhancement, but I'm glad if that is the case.

More to Explore

Administration

Need more information on Administration? Check out the Administrators guide for the Oracle Database