Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1046
  • Last Modified:

oracle listner problem

I have oracle 10g server running on redhat linux 9.0, the problem is that the when trying to connect from the clients its giving the error "ORA-12516: TNS:listener could not find instance with   matching protocol stack.". After restarting the db its works fine. Again the same problem happens after some time. What could be the problem. Please give me a solution for this

thanks in advance

Shaju
0
shajumc
Asked:
shajumc
  • 2
1 Solution
 
sfardinCommented:
How is your Server configured? Is it shared or dedicated?
0
 
sfardinCommented:
copied from Oracle Metalink

Symptom(s)
~~~~~~~~~~
Client connections may intermittently fail with either of the following errors:

TNS-12516 TNS:listener could not find instance with matching protocol stack
TNS-12519 TNS:no appropriate service handler found

Additionally, a TNS-12520 error may appear in the listener log.

TNS:listener could not find available handler for requested type of server

The output of the lsnrctl services command may show that the service handler
is in a "blocked" state.
 
e.g. '"DEDICATED" established:1 refused:0 state:blocked'

Change(s)
~~~~~~~~~~

None necessarily.  Perhaps increase in load.


Cause
~~~~~~~
 
By way of instance registration, PMON is responsible for updating the listener
with information about a particular instance such as load and dispatcher
information.  Maximum load for dedicated connections is determined by the
PROCESSES parameter.  The frequency at which PMON provides SERVICE_UPDATE
information varies according to the workload of the instance.  The maximum
interval between these service updates is 10 minutes.  

The listener counts the number of connections it has established to the instance
but does not immediately get information about connections that have terminated.  
Only when PMON updates the listener via SERVICE_UPDATE is the listener
informed of current load.  Since this can take as long as 10 minutes, there can be
a difference between the current instance load according to the listener
and the actual instance load.  

When the listener believes the current number of connections has reached maximum
load, it may set the state of the service handler for an instance to "blocked"
and begin refusing incoming client connections with either of the following
errors:

TNS-12516 TNS:listener could not find instance with matching protocol stack
TNS-12519 TNS:no appropriate service handler found

Additionally, a TNS-12520 error may appear in the listener log.

The output of lsnrctl service may show that the service handler is "blocked".
 
e.g. '"DEDICATED" established:1 refused:0 state:blocked'

Fix
~~~~

Increase the value for PROCESSES.
0
 
schwertnerCommented:
This is a bug in 10g and will be fixed in next releases. I experience the same problem with 10g on Windows/2000.
The problem arises when we shutdown the instance and after that bounce it.  In this case we have to restart the box - fun!
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now