The only reason I can think of is "Its NT" ;-) The advantage is "Reboot" is
the answer to all your problems ;-)

Anyways, we had a similar problem.
1. Check up Metalink on disabling trace and deleting .dat files.
2. Check the number of process.
3. check up Metalink on modifying a few listener.ora and sqlnet.ora
parameters.

Having said that, they did not work for us. Until we discovered that we hit
the error whenever the virtual memory approached 1.7Gb. NT Standard Edition
has a memory limitation of 2Gb, that can be utilized by a process. Also,
looking at the threads in NT performance monitor, we noticed that the
number of threads kept on increasing for the Oracle process. Memory Leak,
ungraceful disconnections, I dont know??? The solution was always a reboot.





"Trilling,
Jeff" To: "LazyDBA.com Discussion" <[Email Address Removed]
<[Email Address Removed] cc:
ynj.gov> Subject: corrupted listener???

March 28,
2002 01:59 PM






Dear Gurus -
All of a sudden my users can't connect and get:
TNS-12500: TNS:listener failed to start a dedicated server
process
I did a lsnrctl status and it says the service handlers are up.
I
did lsnrctl stop, lsnrctl start and lsnrctl reload. I shut down the
listener
service (NT) and restarted, Nothing seemed to help. I can connect to the
database from the server but not from any of the clients. I turned on
tracing but nothing seems abnormal. I shut down the database and restarted
and this did not help. The only remedy was a reboot of the server which
corrected the problem. Any body seen this ? Ora-817 NT4 - Thanks in advance
- Jeff



Oracle LazyDBA home page