Switchover take too long

Question

Dear gurus,
I'd like to do switchover on my dataguard. but at first step in primary, when i typed 'SQL> alter database commit to switchover to physical standby with session shutdown;' the process stuck for about 2 hours and hasn't finished yet till now.
what's wrong with my dataguard. it took long time to perform switchover. please help me.
Thanks,
Andes

Answer 1

Hi..
**Select thread#,max(sequence#) from v$log_history group by thread#; from both the standby and the production database.**
on primary :
SQL> Select thread#,max(sequence#) from v$log_history group by thread#;
THREAD# MAX(SEQUENCE#)
1 5627
on standby :
SQL> Select thread#,max(sequence#) from v$log_history group by thread#;
THREAD# MAX(SEQUENCE#)
1 5171
**select sequence#,applied from v$archived_log where applied='YES'; -- on standby database.**
in this part, i tried on both server, i list eight line from below.
ON STANDBY :
SEQUENCE# APP
5163 YES
5164 YES
5165 YES
5166 YES
5167 YES
5168 YES
5169 YES
5170 YES
118 rows selected.
ON PRIMARY :
SEQUENCE# APP
5158 YES
5160 YES
5161 YES
5163 YES
5164 YES
5165 YES
5166 YES
5167 YES
5168 YES
5169 YES
5170 YES
2233 rows selected.
**Also, are all the archive logs that are generated on the production but not yet applied to the standby database are present in on the standby archive log destination.Have you canceled the switchover command.**
yes, i've canceled the switchover command. i'm not sure about the archive log that not yet applied to the standby database are present on both servers, coz i made schedule on crontab that erase archive log on every day at 3 AM.
what is ur suggest ? Thanks in advance.