Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Listener.log size limit on Linux 64-bit

Marko SuticJun 27 2009 — edited Jul 24 2013
Hi!

We have listener.log file growing very fast because of very active database. Every month or two I truncate that file to free up disk space but this time I forgot to truncate it for some time.

File grew to 4294967352 bytes and stopped there on that size. Everything is working as it should with listener service - only listener.log file isn't updating.


I've tried to search for more informations about listener.log size limit but haven't found answer that satisfies me.

Where can I find more information why my listner.log file is limited to 4294967352 bytes?

I suppose that this is some OS limit but how can I check this?

It is Linux 64-bit OS with Oracle 10.2.0.4.

Thanks for possible answers and best regards,
Marko Sutic

Comments

ivwvi
schedule a job which backup /compress/remove old listener.log.
os level file limit
ulimit -a <<<<<not sure most of time it show unlimited
Marko Sutic
I will schedule job which will take care of big listener.log - maybe configure logrotate for managing big logs (this isn't a problem).

About ulimit -a command. I've executed it shows:
file size (blocks, -f) unlimited

Thanks for your answer,
Marko
41933
I think the os file system limit the file size,
there is different largest file size in every filesystem.
669771
Hi,

limit depends on your OS.There are limits on SUSE
http://www.suse.de/~aj/linux_lfs.html

Regards,
Tom
Marko Sutic
Yes you are both correct.
I've searched more information about file size limitations and found out that there are certain limits for different kind of OS-es.


I've truncated listener.log with "cat /dev/null > listener.log" without stopping process and freed disk space.

Now I have empty listener log and new log updates are not appending into file?!
I know that probably process restart will fix the problem but I wanted to truncate log file without process restart.

Besides that everything works as it should.
Hm... I have to examine that Oracle behavior.

Thanks and regards,
Marko
unknown-698157
You can set the log file name to a different name using lsnrctl.
Other than that you have to stop and restart the listener.

--------------------------
Sybrand Bakker
Senior Oracle DBA
Marko Sutic
Ah, yes... thanks Sybrand for reminder, my brain just stopped working :)

Just resolved my problem:

LSNRCTL> set current_listener LISTENER_DB
Current Listener is LISTENER_DB
LSNRCTL> set log_file listener_db1
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.2.10.40)(PORT=1521)))
LISTENER_DB parameter "log_file" set to listener_db1.log
The command completed successfully
LSNRCTL> set log_file listener_db
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.2.10.40)(PORT=1521)))
LISTENER_DB parameter "log_file" set to listener_db.log
The command completed successfully
LSNRCTL>


Regards,
Marko
Mark D Powell

There is no need to stop and restart the listener to remove the listener.log.  Just stop logging via lsnrctl [set log_status off], remove the file, restart logging.

HTH -- Mark D Powell --

1 - 8
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Aug 21 2013
Added on Jun 27 2009
8 comments
14,123 views