Grid Control and Target:Database page

#41

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

HI Dan,
Well - the database is indeed dynamically registering with the
listener:

STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 -
Production
Start Date 04-JAN-2008 18:00:31
Uptime 0 days 20 hr. 2 min. 59 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /home/oracle/tnsadmin/listener.ora
Listener Log File /oracle/product/10.2.0.1/network/log/
listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=edgwprd1 )(PORT=1521)))
Services Summary...
Service "edgwrp01" has 1 instance(s).
Instance "edgwrp01", status READY, has 1 handler(s) for this
service...
Service "pgdb" has 1 instance(s).
Instance "pgdb", status READY, has 1 handler(s) for this service...

nothing fancy here - using the default listener, no SID_LIST in the
listener... But Grid insists that database "pgdb" should be using a
different listener (the one that was running when I installed grid and
the agent).

This is from the target:datbase page:
General
[Black Out]
Status Up
Up Since Jan 4, 2008 6:00:35 PM CST
Instance Name pgdb
Version 10.2.0.1.0
Host edgwprd1
Listener EDGWPRD1_10201_edgwprd1
View All Properties

So...any thoughts?
pg

#42

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

HI Dan,
Well - the database is indeed dynamically registering with the
listener:

STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 -
Production
Start Date 04-JAN-2008 18:00:31
Uptime 0 days 20 hr. 2 min. 59 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /home/oracle/tnsadmin/listener.ora
Listener Log File /oracle/product/10.2.0.1/network/log/
listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=edgwprd1 )(PORT=1521)))
Services Summary...
Service "edgwrp01" has 1 instance(s).
Instance "edgwrp01", status READY, has 1 handler(s) for this
service...
Service "pgdb" has 1 instance(s).
Instance "pgdb", status READY, has 1 handler(s) for this service...

nothing fancy here - using the default listener, no SID_LIST in the
listener... But Grid insists that database "pgdb" should be using a
different listener (the one that was running when I installed grid and
the agent).

This is from the target:datbase page:
General
[Black Out]
Status Up
Up Since Jan 4, 2008 6:00:35 PM CST
Instance Name pgdb
Version 10.2.0.1.0
Host edgwprd1
Listener EDGWPRD1_10201_edgwprd1
View All Properties

So...any thoughts?
pg

#43

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

HI Dan,
Well - the database is indeed dynamically registering with the
listener:

STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 -
Production
Start Date 04-JAN-2008 18:00:31
Uptime 0 days 20 hr. 2 min. 59 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /home/oracle/tnsadmin/listener.ora
Listener Log File /oracle/product/10.2.0.1/network/log/
listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=edgwprd1 )(PORT=1521)))
Services Summary...
Service "edgwrp01" has 1 instance(s).
Instance "edgwrp01", status READY, has 1 handler(s) for this
service...
Service "pgdb" has 1 instance(s).
Instance "pgdb", status READY, has 1 handler(s) for this service...

nothing fancy here - using the default listener, no SID_LIST in the
listener... But Grid insists that database "pgdb" should be using a
different listener (the one that was running when I installed grid and
the agent).

This is from the target:datbase page:
General
[Black Out]
Status Up
Up Since Jan 4, 2008 6:00:35 PM CST
Instance Name pgdb
Version 10.2.0.1.0
Host edgwprd1
Listener EDGWPRD1_10201_edgwprd1
View All Properties

So...any thoughts?
pg

#44

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

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

#45

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

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

#46

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

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

#47

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

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

#48

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

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

#49

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

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

#50

On Jan 5, 12:15 pm, DA Morgan <damor... (AT) psoug (DOT) org> wrote:

Quote:

pgodfrin wrote:
On Jan 4, 10:45 pm, DA Morgan <damor... (AT) psoug (DOT) 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...@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...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

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