|
It's possible. I've heard of this happening before
and the recommendation was to clear out the listener.log file. There are a
couple of ways to clear out that file. One is to stop the listener and delete
it. The other is to cat /dev/null to it (i.e. cat /dev/null > listener.log).
The latter doesn't require the listener to be stopped. This works in Unix. On
windows I think the only option is to stop the listener and delete the
file.
----- Original Message -----
Sent: Tuesday, March 04, 2003 12:04
PM
Subject: Listener Hangs
We are running Oracle 7.3.4.5.0 on
an IBM/AIX RISC System/6000: Version 2.3.4.0.0.
Yesterday morning our LISTENER
process hung. “ERROR: ORA-12203: TNS:unable to connect to destination”.
We resolved the problem using the following steps:
a)
Stop Listener using LSNRCTL
utility (this hung – did not succeed in stopping the
listener)
b)
Issue UNIX command kill -9
<process id> to kill the corresponding Listener process.
c)
Start the listener using the
LSNRCTL utility
I checked the alert log and
listener log. I found nothing in either file pointing to what the
problem might have been. However, I did note that the listener.log file
was 200 MB in size. Would the large size of the listener.log file
contribute to the Listener hanging? This problem has occurred 6 to 8
times in the past couple of weeks. I do plan on starting a new
listener.log file.
Thanks,
Sam Bootsma
[EMAIL PROTECTED]
|
