Re: Listener.log

Don't know if this is what you're looking for, but the two parameters you need are in the LISTENER.ORA file:

LOG_DIRECTORY_listener_name

Purpose:
 Controls the directory for where the log file is written. Default Value:
 Current directory where executable is started from. Example:
 log_directory_listener=/oracle/traces

LOG_FILE_listener_name

Purpose:
 Specifies the filename where the log information is written Default Value:
 listener_name.log
Example:
 log_file_listener=lsnr

And then, I suspect, you need to execute 'lsnrctl reload' as you mentioned below in order for the changes to take effect. The docs mention the following about the RELOAD command:

This command shuts down everything except listener addresses, and re-reads the LISTENER.ORA file. This command enables you to add or change services without actually stopping the listener.

However, it also says that this won't work on 'valid nodes' (whatever that means)...

HTH,
SR    

On Mon, 30 Oct 2000 14:56:59 -0800, spaz <spaz_at_yahoo.com> wrote:

>Quick, hopefully simple question in terms of listener.log file
>
>Running Oracle 8 on Solaris 2.6
>
>Why isn't the listener.log file the same as the alert<SID>.log file in
>terms of
>being able to move this file and have the listener start logging to a
>new file?
>
>It won't even log to listener.log if you rename it, and create another
>listener.log file.
>The listener will log to the file you just renamed it to.
>
>I know with the alert log, you can just move it, Oracle will create a
>new on and start logging away. What's the difference. Is the solution
>a lsnrctl reload?
>
>Thanks.
>
>
Received on Mon Oct 30 2000 - 19:06:06 CST