LISTENER LOG

[ndisang]

I have PATROL that monitors some features on my database. It is creating a listener log almost every minute and its now in hundreds of megs.
Questions;
1/ Can I remove the listener.log (as you can you with the alert.SID.log) and it would generate a new one once needed?
2/ should I re-direct the listener log location from within listener.ora file? Which is the better option. I would prfer the first but what do you think? Or is there a third?
Thanks

24-MAR-2002 03:36:17 * service_register * prod2 * 0
24-MAR-2002 03:36:20 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=ccsp2)(USER=ora
OMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=135290880)) * stat
24-MAR-2002 03:37:39 * (CONNECT_DATA=(SID=prod2)(CID=(PROGRAM=)(HOST=ccsp
=patrol))) * (ADDRESS=(PROTOCOL=tcp)(HOST=134.192.240.101)(PORT=48588)) *
ish * prod2 * 0
24-MAR-2002 03:37:40 * (CONNECT_DATA=(SID=prod2)(CID=(PROGRAM=)(HOST=ccsp
=patrol))) * (ADDRESS=(PROTOCOL=tcp)(HOST=134.192.240.101)(PORT=48589)) *
ish * prod2 * 0
24-MAR-2002 03:38:01 * (CONNECT_DATA=(SID=prod2)(CID=(PROGRAM=)(HOST=ccsp
=patrol))) * (ADDRESS=(PROTOCOL=tcp)(HOST=134.192.240.101)(PORT=48596)) *
ish * prod2 * 0
24-MAR-2002 03:38:02 * (CONNECT_DATA=(SID=prod2)(CID=(PROGRAM=)(HOST=ccsp
=patrol))) * (ADDRESS=(PROTOCOL=tcp)(HOST=134.192.240.101)(PORT=48597)) *
ish * prod2 * 0
24-MAR-2002 03:38:03 * (CONNECT_DATA=(SID=prod2)(CID=(PROGRAM=)(HOST=ccsp
=patrol))) * (ADDRESS=(PROTOCOL=tcp)(HOST=134.192.240.101)(PORT=48598)) *
ish * prod2 * 0
24-MAR-2002 03:38:04 * (CONNECT_DATA=(SID=prod2)(CID=(PROGRAM=)(HOST=ccsp
=patrol))) * (ADDRESS=(PROTOCOL=tcp)(HOST=134.192.240.101)(PORT=48600)) *
ish * prod2 * 0
24-MAR-2002 03:38:05 * (CONNECT_DATA=(SID=prod2)(CID=(PROGRAM=)(HOST=ccsp
listener.log (2%)

[aarroyob]

The best option is:

Stop the listener
Drop,move or that you want the listener.log file
Start the listener --> Oracle will generate a new one

By this, the users are relative not affected, because only new connection will have problems.

Cheers

Angel

[jovery]

If you don't want to interupt the listener process, you can use the following method.

> lsnrctl set log_status off

delete the log

> lsnrctl set log_status on

This will remove the file without having to stop/start the listener

Regards

[Jr]

1/ Can I remove the listener.log (as you can you with the alert.SID.log) and it would generate a new one once needed?

YES.

2/ should I re-direct the listener log location from within listener.ora file? Which is the better option. I would prfer the first but what do you think?

Depends on situation.
You can always change the log file directory by setting
LOG_DIRECTORY in the listener.ora file.
You can also change the LOG_DIRECTORY value dynamically using lsnrctl utility.
Alway prefer LSNRCTL reload ( where ever applicable ) - this will not down the listener.

Jr.

[aarroyob]

Originally posted by jovery
If you don't want to interupt the listener process, you can use the following method.

> lsnrctl set log_status off

delete the log

> lsnrctl set log_status on

This will remove the file without having to stop/start the listener

Regards

Very good remark Jim. I didn´t know this command. It doesn't appear with help in lsnrctl.

Regards

Angel

[marist89]

Originally posted by Jr

1/ Can I remove the listener.log (as you can you with the alert.SID.log) and it would generate a new one once needed?

YES.

Ah, kind of yes, kind of no.

If you are on some Unix platforms, the listener will keep writing to the listener.log even though it is deleted. It will not generate a new listener.log until you bounce the listener.

This is different than the alert.log in that the alert.log will generate a new file as soon as it needs to write something.

[ndisang]

A million thanks to all of you out there.