Thanks Carel. That explain's it all. On 9/20/05, Carel-Jan Engel <cjpengel.dbalert@xxxxxxxxx> 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 > -- > //www.freelists.org/webpage/oracle-l > > >