pcp
[Top] [All Lists]

Re: [pcp] Oracle connection debugging (was Re: Handling Oracle PMDA Late

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, Marko Myllynen <myllynen@xxxxxxxxxx>
Subject: Re: [pcp] Oracle connection debugging (was Re: Handling Oracle PMDA Latencies)
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 23 May 2016 01:37:43 -0400 (EDT)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <573DB974.3080501@xxxxxxxxxx>
References: <56F25541.9020602@xxxxxxxxxx> <57175FC8.2000600@xxxxxxxxxx> <1558022602.42320984.1461208897951.JavaMail.zimbra@xxxxxxxxxx> <57395F04.2090909@xxxxxxxxxx> <1695396289.47966126.1463381940778.JavaMail.zimbra@xxxxxxxxxx> <573D897A.5070804@xxxxxxxxxx> <573DB415.7000807@xxxxxxxxxxxxxxxx> <573DB974.3080501@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: pN4BkefDQRBuJXgjX8t3A0zJDzSajQ==
Thread-topic: Oracle connection debugging (was Re: Handling Oracle PMDA Latencies)

----- Original Message -----
> Hi,
> 
> On 2016-05-19 15:39, Ken McDonell wrote:
> > On 19/05/16 19:38, Marko Myllynen wrote:
> >> ...
> > 
> > Just a reminder, two-threaded PMDAs (one for PMCD, one for SQL) and
> > PM_ERR_PMDANOTREADY were invented in the first place to accommodate slow
> > DBMS PMDAs.

(Twas introduced for slow startup originally though, IIRC, is that right?
In Markos case, several queries seem to be permanently slow).

> Thanks for pointing that out - Nathan, does this sound at all feasible
> /helpful for the Oracle PMDA?

Its something we might use, but its operating mainly under the assumption
that slowness is transient and its all about getting an error to the client
when the database is slow to respond (while the PMDA keeps going, instead
of timing out).  In the case of the system here, we'll get lots of instances
of that error code & not so much useful values.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>