Re: OMS Discovery and standby databases

From: Jes Challand <jesc99_at_budweiser.com>
Date: 1 Nov 2002 07:10:18 -0800
Message-ID: <598cde14.0211010710.547cd2c3@posting.google.com>

As I'm reluctant to change anything affecting my live database until I understand all the implications, I have just made the following changes to the init.ora on my standby database -

SQL-P >show parameter db_domain

NAME                                 TYPE    VALUE
------------------------------------ ------- 
db_domain                            string  LUBSSTANDBY.LUBS.CO.UK

SQL-P >show parameter global_names

NAME                                 TYPE    VALUE
------------------------------------ ------- 
global_names                         boolean TRUE

and changed the standby server's listener.ora to contain - (SID_DESC =

      (GLOBAL_DBNAME = P.LUBSSTANDBY.LUBS.CO.UK)
      (ORACLE_HOME = /app/oracle/product/8.1.7)
      (SID_NAME = P)

Unfortunately, in OEM I can still only discover one host at a time. The database on lubsstandby is being discovered as P (not P.LUBSSTANDBY.LUBS.CO.UK as I was expecting). Also, on my LIVE database -
SQL-P >select * from global_name;

GLOBAL_NAME

I know I can change this with 'alter database rename global_name to P.<live server>.<domain>' on my live database, but presumably this will be shipped to standby in archive logs and will be incorrect there. I also can't change it on standby without opening the database, which I can't do because it's a standby database etc etc !!!!

Am I missing something ? Thanks in advance.

jesc99_at_budweiser.com (Jes Challand) wrote in message news:<598cde14.0210310852.9f4dc50_at_posting.google.com>...
> Thanks koert54.
> Before I do anything to affect my live and standby databases, I want
> to understand the impact of the change in a non-critical environment
> so I've done the following on a test database -
> added an init.ora parameter of db_domain as LUBSSTANDBY.LUBS
> alter database rename global_name to DBA1.LUBSSTANDBY.LUBS;
> added GLOBAL_DBNAME = DBA1.LUBSSTANDBY.LUBS to listener.ora.
> How can I prove that everything is functioning as expected ?
> Access to my live database is resolved via tnsnames on each client. Is
> this affected by any of the changes above ?
> Thanks in advance.
> "koert54" <nospam_at_spam.com> wrote in message news:<b1Zr9.168267$8o4.26259_at_afrodite.telenet-ops.be>...
> > Yes ..
> >
> > You should use fully qualified dbnames !
> > This means specifying db_domain (init.ora), using global_dbname
> > (listener.ora) etc.
> > All my databases are name <instance_name>.<server_name>.<domain_name> - it's
> > sometimes
> > a bitch to use but necessary with standby DB's ...
> >
> > cheers
> >
> > "Jes Challand" <jesc99_at_budweiser.com> wrote in message
> > news:598cde14.0210180542.7654cde8_at_posting.google.com...
> > > Hi, I have a problem similar to one raised on a posting in Aug. 2002,
> > > but with one additional consideration.
> > >
> > > I'm running 8.1.7.2 on two E450s running Solaris 8. On my live server,
> > > I have only one database - with a SID and global name of P. On my test
> > > server I have five test databases and a standby database (normally
> > > mounted) as DR for my live database - also with a SID and global name
> > > of P.
> > > I've just set up my OMS and intelligent agent and auto-discovered all
> > > the services on my test server. When I try to discover the database on
> > > my live server, it fails with the VD-4520 reported in a previous
> > > posting.
> > > Having deleted the test server and stopped and started the IAs, I can
> > > discover the live server and database, and hence can 'flip' between
> > > the two. The only way I can discover both at the same time is to
> > > comment the entry for one of the P databases from the respective
> > > server's oratab - not desirable.
> > > Has anyone else managed to discover both databases in a live/standby
> > > configuration ?
> > > TIA
Received on Fri Nov 01 2002 - 09:10:18 CST