Re: listener - lsnrctl reload drops dynamic service handlers

The documents that I quoted, specifically state that, "without actually stopping the listener" which is different to what you said which is, "Basically a reload is a stop followed by a start".

I wish that the documents were more specific in that they don't state (or I can't find) when the dynamic services will be registered after the reload command is issued - "...listener will be unregistered and subsequently registered again...". I had assumed that this would be straight away but I have found that this is not the case.

With the ever increasing use of dynamic registration, I believe that the documentation is lacking, and could cause downtime, in that it should state that dynamically reliant services could be unavailable for up to a minute at a time (and I have found this to be longer when the listener is experiencing high loads). Instead this is not mentioned at all.

This brings me back to my original question, which is, does the lsnrctl reload command drop dynamic service handlers thus making dynamically registered databases unavailable for a certain period of time (a supposedly maximum period of 1 minute)?

"Sybrand Bakker" <gooiditweg_at_nospam.demon.nl> wrote in message news:de607vk3gi7u4b18uta2rapvqgrg5ii6nb_at_4ax.com...
> On Thu, 13 Mar 2003 14:21:44 +1000, "Peter" <no_email_at_no_email.com>
> wrote:
>
> >I'm wondering if the lsnrctl reload command is suppose to drop
dynamically
> >registered services and then wait for the database to re-register
(meaning a
> >possible few minute wait) these with the listener or is this an oracle
> >listener bug on the following system?
>
>
> It is a feature, which is described nicely in the docs you quote.
> Basically a reload is a stop followed by a start, and it has always
> been a stop followd by a start. This would of course result in wiping
> mts connections.
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Thu Mar 13 2003 - 00:46:21 CST