Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Intermittend ORA-12519, TNS:no appropriate service handler found
Robert Klemme wrote:
> Hi all,
>
> we have an Oracle 10 (version details below) on Linux (RHEL 4). When
> connecting via JDBC we get intermittend ORA-12519 (reflected as TNS-12519
> in listener.log). sqlldr also has a problem, although at the moment I
> can't exactly determine whether it's the same (I'm guessing it is because
> the happen about the same time).
>
> Research on the web revealed that a too low value for "processes" might be
> the reason. (The other possible cause I found was non matching versions of
> DB and client but this is not the case here.) So we increased DB param
> "parallel_max_servers" to 200. Since the error still showed up we went up
> to 400. It's been quiet since the last change of this parameter on
> Tuesday but some minutes ago I got an email notification that the error
> occurred again.
>
[snip]
12519, 00000, "TNS:no appropriate service handler found"
// *Cause: The listener could not find any available service handlers that // are appropriate for the client connection. // *Action: Run "lsnrctl services" to ensure that the instance(s) have // registered with the listener, and are accepting connections.
And what does the manual say about parallel_max_servers?!?
PARALLEL_MAX_SERVERS Parameter type Integer
Default value Derived from the values of CPU_COUNT, PARALLEL_AUTOMATIC_TUNING, and PARALLEL_ADAPTIVE_MULTI_USER
Parameter class Static
Range of values 0 to 3599
Real Application Multiple instances must have Clusters the same value.
Note:
This parameter applies to parallel execution in exclusive mode as well
as in the Oracle9i Real Application Clusters environment.
PARALLEL_MAX_SERVERS specifies the maximum number of parallel execution processes and parallel recovery processes for an instance. As demand increases, Oracle increases the number of processes from the number created at instance startup up to this value.
If you set this parameter too low, some queries may not have a parallel execution process available to them during query processing. If you set it too high, memory resource shortages may occur during peak periods, which can degrade performance.
Do you really think one has *anything* to do with the other?!?
Instead of searching the web, you should read the manual. All manuals can be found at http://tahiti.oracle.com
-- Regards, Frank van Bortel Top-posting is one way to shut me up...Received on Fri Feb 24 2006 - 13:09:12 CST