Re: TNS-12541 after listener goes idle...!

In article <813jpq$ka8$1_at_nnrp1.deja.com>,   Guy Boulais <ve2gyb_at_my-deja.com> wrote:
> I've got a really strange problem:
>
> I've setup Oracle 8.0.5 on a Sun Enterprise 450 with 4 CPU and
> 1.5Gb of RAM, 2 databases are running and 1 listerner.
>
> If I start the listener, workstations can access databases.
> BUT, If nothing is happening on the listener for a while
> and workstations try to access databases they receive:
> TNS-12541: TNS:no listener
>
> If I tnsping from the server it's OK!
>
> I found that 2 ways can re-activate the listener:
> -stop and restart the listener via lsnrctl
> -starting SQL*Plus locally on the server by forcing use of listener
> (sqlplus system_at_cltup201.world)
>
> What could cause the listener to idle-out and not respond remote
> client?
>
> Any clue?
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

Does $ORACLE_HOME/network/log/listener.log say anything interesting? Are your users properly exporting ORACLE_SID and/or TWO_TASK (export command in ksh, setenv in csh)?

Are you using onames with a non-matching fallback database? (or perhaps your onames is going sleepy-bye and users are falling back to a tnsnames.ora that is obsolete)?

I've seen this error along with TNS00517 if there are just too many processes running.

jg

--
These opinions mine
mailto:joel-garry_at_nospam.home.com
Remove nospam to mail
http://ourworld.compuserve.com/homepages/joel_garr

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Fri Nov 19 1999 - 15:53:03 CST