In case of disaster with Primary Database site, or not available for production for any reason then we can activated standby database as a primary production database.
Note: If you are trying to activate standby database for production use, please get permission from senior authority to do so.
Previously, we covered “Incremental backup from SCN – Oracle 11g Manual Data Guard Part-IV”.
Copy archive logs from primary database, those yet to apply on standby database before activate it.
Cheers!! Standby database successfully activated as Primary database. Failover successful.
Post activity check, ensure database mode and role, it should be READ WRITE and PRIMARY.
Note: Please perform full database backup after failover.
Note: Once old primary database is available for use then you can reconfigure standby database.
Simply you can’t apply archive logs to standby database server when database is in READ ONLY mode, but you can continue to transfer your archive logs to standby database server, Once your standby database back to MOUNT mode than you can apply your remaining archive logs.
Previously, We covered Manual data guard switch over and switch back activity step by step approach.
The database is in mount state and its role is Physical Standby, as expected, good to go.
Transfer all remaining archive logs from the primary database server to standby database server and apply it (If there is an archive log gap), before opening a standby database to READ ONLY mode. For more information on it, you can refer Step – XVI from my one of post on “Configuring Manual Data Guard”.
Repeat Step-I to verify standby database mode and its role.
Stay tuned with my next article on Incremental backup from SCN.
2 VM’s, PR and DR with enough CPU and RAM in order to run oracle database.
db_unique_name on standby and primary database should be different.
Primary and Standby server should ping each other by IP as well as its server name. In order to ping with its server name, edit /etc/hosts file accordingly.
Verify your database is in Archive Log Mode or NO archive log mode, if not than my one of the post will help you to configure your Oracle 11g database is in archive log mode. Primary database need to be in Archive log mode.
Create parameter file(i.e. initRTS.ora) on Primary database(Hostname:PR). If you are not using spfile than skip this step.
Create Required Directory Structure on standby database server(Hostname: DR). In my case I am going to replicate same directory structure as mentioned in parameter file.
In case of your datafile and logfile location on standby is different from primary than add following parameter to initRTS.ora file.
On standby database, Practically there is no backup taken from RMAN, but if you issue following command to list out existing backups, than RMAN will show you full database backup information of primary database.(Step – III) Because RMAN repository is stored in control file and we have copy pasted standby control file from primary to standby database.
Above recovery session will be end up with RMAN error message like mentioned below. Recovery successful.
Cheers!! Our Manual Data Guard configuration have configured successfully.
All transfered archive logs have applied on standby database successfully, now check maximum of sequence number of applied archived log.
Maximum of sequence number of applied archived log on primary and standby is same, our configuration successful. Cheers!!!
Your comment and suggestion are highly appreciated.
Stay Tuned with my next article on “Switch over and switch back – Oracle 11g Manual Data Guard Part-II“.