Rotating Oracle Listener.log file

Oracle database logs doesn’t rotate by it self.
As time goes by, the server may hold logs that are too big to read and takes too much storage space.
This can get your server to a maximum capacity or cause the listener can't start.

The best solution is to use logrotate:

There are 2 log files needs to be rotate:
Alert log and Listener log

Create new logrotate rules by edit a files under /etc/logrotate.d/

/etc/logrotate.d/oracle-alert

# Logrotate file for Oracle Alert

/home/oracle/admin/[SID]/bdump/alert_[SID].log {
    missingok
    weekly
    rotate 4
    compress
    delaycompress
    create 640 oracle oinstall
}

/etc/logrotate.d/oracle-listener

# Logrotate file for Oracle Listener

/home/oracle/product/10.2.0/network/log/listener.log {
    missingok
    daily
    rotate 31
    compress
    delaycompress
    create 644 oracle oinstall
    prerotate
        su - oracle -c "lsnrctl set Log_status off"
    endscript
    postrotate
        su - oracle -c "lsnrctl set Log_status on"
    endscript
}

Notice:delaycompress
This command can be useful if you want the archived logs to be compressed, but not right away.
With "delaycompress" active an archived log won't be compressed until the next time the log is rotated.
Note that "delaycompress" only works if you also have "compress" in your config.

To test it out:
/usr/sbin/logrotate -vdf /etc/logrotate.conf

To force run it:
/usr/sbin/logrotate -vf /etc/logrotate.conf

Reference:
http://articles.slicehost.com/2010/6/30/understanding-logrotate-on-centos-part-1
http://articles.slicehost.com/2010/6/30/understanding-logrotate-on-centos-part-2