Re: Intermittend ORA-12519, TNS:no appropriate service handler found

Frank van Bortel wrote:
> shortcutter_at_googlemail.com wrote:
>> Yes. First of all, the setup works normal most of the time, so the
>> registration has actually taken place (this is true even after the
>> intermittend failure). Also, the listener is local and firewall rules
>> are ok (=> no network problems). Second, it was explained that the
>> error will occur if "processes" is set too low. Third, the parameter
>> "processes" is derived from "parallel_max_servers" (indicated by
>> online doc, and you cannot change it directly via EM). Fourth, we
>> actually saw an improvement because before we changed the value we
>> saw the error more frequently.
>>
>
> "Most of the time" ... ok, you investigate then.

That's exactly what I am trying but until now I didn't see any hint as to *how* to investigate this.

> Listener been down? DB been down?

Nope.

> Registration takes time, you know.

Guess so.

> And if it's local, then why bother with a listener *at all*?!?

The listener is local to the db server. The application sits on a different machine.

> And if it's local, then what would a firewall have to do
> with it? You're local, you shouldn't even see your
> packets on the net. Switch to bequeath, it's faster, too.

With iptables it's actually possible to close the loopback device and thus to prevent even local communication. I just wanted to exclude a possible cause of connection problems. That's why I mentioned it.

> And if you (still) believe processes could be too low,
> then increase that, not your parallel_max_servers.
>
> And your improvement is coincidence, nothing else

I'd be glad for a hint to actually verify that. Any tracing or debugging I can do?

    robert Received on Mon Feb 27 2006 - 02:34:34 CST