In database production, the log of listener was grow rapidly, some times if you move the “listener.log” while the listener is up and running, listener will stop writing to log file after you move/delete the “listener.log”, it won’t create new log file.
The listener log status will be ‘off’, You need to start the “listener log” again manually. For this reason you must do this procedure.

$ lsnrctl stat

LSNRCTL for Solaris: Version 9.2.0.6.0 - Production on 09-MAR-2008 12:43:22

Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
STATUS of the LISTENER
————————
Alias LISTENER
Version TNSLSNR for Solaris: Version 9.2.0.6.0 - Production
Start Date 11-SEP-2007 03:34:17
Uptime 180 days 9 hr. 9 min. 4 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File /oracle/app/product/9.2.0/network/admin/listener.ora
Listener Log File /oracle/app/product/9.2.0/network/log/listener.log
Listening Endpoints Summary…
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=VASMdbz)(PORT=1521)))
Services Summary…
Service “PLSExtProc” has 1 instance(s).
Instance “PLSExtProc”, status UNKNOWN, has 1 handler(s) for this service…
Service “DB_SID.domain.com” has 2 instance(s).
Instance “DB_SID”, status UNKNOWN, has 1 handler(s) for this service…
Instance “DB_SID”, status READY, has 1 handler(s) for this service…
The command completed successfully

$ lsnrctl
LSNRCTL> set log_status off

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
LISTENER parameter “log_status” set to OFF
The command completed successfully

$ mv /oracle/app/product/9.2.0/network/log/listener.log /backup/listener.log_9-March-2008

LSNRCTL> set log_status on

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
LISTENER parameter “log_status” set to ON
The command completed successfully

Popularity: 55% [?]

You Should Also Check Out This Post:

More Active Posts: