Re: Grid Control and Target:Database page

From: pgodfrin <pgodfrin_at_gmail.com>
Date: Sat, 5 Jan 2008 12:21:16 -0800 (PST)
Message-ID: <f6b3db4d-ae20-45ee-8c8b-47c1db2d95de_at_i12g2000prf.googlegroups.com>


[Quoted] On Jan 5, 12:15 pm, DA Morgan <damor..._at_psoug.org> wrote:
> pgodfrin wrote:
> > On Jan 4, 10:45 pm, DA Morgan <damor..._at_psoug.org> wrote:
> >> pgodfrin wrote:
> >>> This is a Fedora 8 installation with Grid 10.1.0.4 (yeah, I know - I
> >>> need to patch it...).
> >>> regards,
> >>> pg
> >> We agree. Go to metalink. Download it. Apply it.
> >> --
> >> Daniel A. Morgan
> >> Oracle Ace Director & Instructor
> >> University of Washington
> >> damor..._at_x.washington.edu (replace x with u to respond)
> >> Puget Sound Oracle Users Groupwww.psoug.org
>
> > oops - Grid is 10.1.2.0.2 ...maybe I dont need to patch it...
>
> > Maybe I can rephrase the question - how does Grid identify that a
> > database should be using a particular listener?
>
> It doesn't. These days databases dynamically register with listeners in
> most cases. It may be looking at where the dynamic registration took place.
> --
> Daniel A. Morgan
> Oracle Ace Director & Instructor
> University of Washington
> damor..._at_x.washington.edu (replace x with u to respond)
> Puget Sound Oracle Users Groupwww.psoug.org

[Quoted] [Quoted] Check it out - went to all targets, deleted the 'offending' listener, then the target:database page did indeed show the current listener... More testing on the way. You can say, "ok - problem solved" - but now I want to be able to have a less GUI intense way of having Grid recognize configuration changes...

pg Received on Sat Jan 05 2008 - 21:21:16 CET

Original text of this message