Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Not Allowed Status DG Switchover

Re: Not Allowed Status DG Switchover

From: Chirag DBA <chiragdba_at_gmail.com>
Date: Wed, 21 Sep 2005 15:23:07 -0400
Message-ID: <1a36296005092112237c851a70@mail.gmail.com>


okie,
 one more time removed the configuration and bounced the standby, created the new configuration.
 Everything is running up and fine now.
 regards - chirag

 On 9/21/05, Chirag DBA <chiragdba_at_gmail.com> wrote:
>
> Hi Team,
> I have a question for the same., I have switched over to the standby.
> But now I am unable to make that physical as standby. I have 2 standbys.
> Now when I create the configuration on the new primary, it is telling me
> that one or more sites has warnings,
> and when I am watching the logs in bdump, it tells me that all the
> parameters showed in show resource command are not in sync. I don wanna set
> all the parameters manually everywhere.
> I have removed the configuration and sites again on primary, deleted old
> dr?SID files on standby and brought back the db in managed recovery mode.
> But no luck , as this is the same thing working previously.
> I am able to do tnsping to both the servers.
> Any idea ???
>
> Regards - Chirag
> On 9/21/05, Stalin <stalinsk_at_gmail.com> wrote:
> >
> > Thanks Carel. That explain's it all.
> >
> > On 9/20/05, Carel-Jan Engel <cjpengel.dbalert_at_xs4all.nl > wrote:
> > >
> > > Hi Stalin,
> > >
> > > 'Not allowed' is nothing to worry about. It just tells that the
> > > primary hasn't been 'committed to switchover to standby', so in this state
> > > you van only failover, not switchover to the standby.
> > >
> > > You will see, that if you complete the preparation on the primary for
> > > a switchover, the standby will show 'TO PRIMARY' as switchover status. By
> > > then you can 'commit to switchover to primary' the standby.
> > >
> > > This is documented in chapter 14 ('VIEWS') of the Data Guard concepts
> > > and administration guide (maybe another chapter number for 10g, I had only
> > > 9iR2 docs at hand here).
> > >
> > > Best regards,
> > >
> > > Carel-Jan Engel
> > >
> > > ===
> > > If you think education is expensive, try ignorance. (Derek Bok)
> > > ===
> > >
> > > On Mon, 2005-09-19 at 16:02 -0700, Stalin wrote:
> > >
> > >
> > > Hi,
> > >
> > > I'm testing DG switchover with physical standby and i was able to
> > > switch primary to standby without any problems. however after
> > > switchover, query on standby (suppose to be primary before), gave me
> > > the fol output.
> > >
> > > SQL> select force_logging,remote_archive,switchover_status,dataguard_broker
> > > from v$database;
> > >
> > > FOR REMOTE_A SWITCHOVER_STATUS DATAGUAR
> > > --- -------- -------------------- --------
> > >
> > >
> > > YES ENABLED NOT ALLOWED DISABLED
> > >
> > > query on primary (suppose to be standby before)
> > >
> > > FORCE_LOGGING REMOTE_ARCHIVE SWITCHOVER_STATUS
> > >
> > > DATAGUARD_BROKER
> > > ------------- --------------
> > > ------------------------------------------------------------
> > >
> > >
> > > ----------------
> > > YES ENABLED TO STANDBY
> > > DISABLED
> > >
> > > I've verified that logs gets shipped/applied on standby from primary
> > > after switchover. No sequence gaps etc. Wondering, why
> > > switchover_status still has "NOT ALLOWED' on the standby database,
> > >
> > >
> > > when it suppose to have "TO PRIMARY"
> > >
> > > Any pointers is much appreicated.
> > >
> > > Thanks,
> > > Stalin
> > >
> > >
> > >
> > > Platform : 10g EE (10.1.0.4 <http://10.1.0.4/>), Solaris 2.9
> > > --
> > > http://www.freelists.org/webpage/oracle-l
> > >
> > >
> > >
> >
>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Sep 21 2005 - 14:25:24 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US