Re: Listener issue

Faisal Qasim wrote:

> Thanks for the responses.
>
> Listener start is at the end of 'dbstart' script, so database should
> be up at that time. Further this problem occurs very rarely and
> listener log doesn't show any error for auto listener start.
>
> Is there anything else, I can check?

The database can be down or even non-exsitant as far as the listener is concerned during startup. It will start successfully. If the db is started after the listener, the listener will still work fine.

However - if networking is not yet configured or loaded while the listener starts, then it will not work.

For example, if your dbstart and listener startup scripts follow directly after the network startup script, and the network uses DHCP.. there is a change that by the time the listener starts, the DHCP allocated IP address has not yet been bound to the ethernet device.. which means that the listener is binding on an IP address like 0.0.0.0 (which is a broadcast address) or 127.0.0.1 (which only will work for loopback connections) or something else that is not valid.

Try delaying the listener startup as one of the last startup processes.

Or redirect STDOUT and STDERR of the listener startup script to a log file. Add ifconfig or ipconfig commands to it so that the log file can show you what the network status was when the listener was binding to IP and port.

--
Billy