Dealing with Oracle snooping file listener.log problem

If    becomes slow to view Oracle log records when connecting, it may be because this file is too large, more than 2G

Need to clean up regularly (if multiple users, remember to use root, may not have permission)

Check listener.log?

Find /-name listener.log

After inspection, the log data is as high as 2G, because some old OS do not support files above 2GB, so when listener.log files

When you exceed the 2GB, you will be unable to handle the new connection. Although the new operating system will not have this problem, we still need to address it.

Carry out regular treatment and cleaning.

Listener log log file processing

[oracle@localhost home] $lsnrctlLSNRCTL > set log_status offConnecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC1521) LISTENER parameter "log_status" set to OFFThe command completed successfullyLSNRCTL > show log_statusConnecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC1521)) LISTENER parameter "log_status" set to OFFThe command completed successfullyLSNRCTL > exit [oracle@localhost home] $find-name listener.loghome/oracle/app/oracle/diag/tnslsnr/localhost/listener/trace/listener.log [oracle@localhost ~] $cd / home/oracle/app/oracle/ Diag/tnslsnr/localhost/listener/trace/ [oracle@localhost trace] $mv listener.log listener.log.20191127 [oracle@localhost trace] $lslistener.log.20191127 ora_2617_140154513196800.trc [oracle@localhost trace] $lsnrctlLSNRCTL > set log_status onConnecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC1521)) LISTENER parameter "log_status" set to ONThe command completed successfullyLSNRCTL > show log_status Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC1521)) LISTENER parameter "log_status" set to ONThe command completed successfullyLSNRCTL > reloadConnecting to (DESCRIPTION= ( ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC1521)) The command completed successfullyLSNRCTL > exit [oracle@localhost trace] $[oracle@localhost home] $lsnrctlLSNRCTL > set log_status offLSNRCTL > show log_statusLSNRCTL > exit [oracle@localhost home] $find-name listener.log [oracle@localhost trace] $mv listener.log listener.log.20191127LSNRCTL > set log_status onLSNRCTL > reload

After we rename the log file, a new listener.log file is automatically generated. Of course, it can also be emptied, you can first copy the backup, and then empty the process.

Summary

The above is introduced by the editor to deal with the listener.log problem of Oracle monitoring files. I hope it will be helpful to you. If you have any questions, please leave me a message and the editor will reply you in time. Thank you very much for your support to the website!

If you think this article is helpful to you, you are welcome to reprint it, please indicate the source, thank you!