Hi all,
My primary database is on the SAN storage and the SAN is having a firmware upgrade on the coming week.
I have a Active dataguard standby setup using the internal disks of the database server, so in case the SAN firmware upgrade encounter issue ( I can still use the standby without changing the network environment)
I also have the luxury do shutdown the primary database before doing the SAN firmware upgrade. Therefore my only concern is to have all changes flushed to standby so that I can have 0 data lost even if the SAN went down permanently due to firmware upgrade issues.
q1) Is my following steps correct ?
On primary
1) shutdown primary database and startup mount;
2) alter system flush redo to standby;
On standby
3) alter database recover managed standby database cancel;
4) alter database recovery managed standby database finish;
5) SELECT SWITCHOVER_STATUS FROM V$DATABASE; -- return either TO PRIMARY or SESSIONS ACTIVE
q2) Beside the above, how do we verify that both databases are actually in sync ?
- checking V$ARCHIVE_GAP in standby ? or
- checking v$datafile_header.checkpoint_change# in both PRIMARY and STANDBY ?
=================================
If SAN storage upgrade fail
On standby
6) ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;
7) ALTER DATABASE OPEN;
if SAN storage upgrade pass
On Primary
6) STARTUP DATABASE;
On Standby
7) ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;
Right ?
Regards,
Noob