Primary Mlog entries after a crash and recovery
edited Jan 23, 2013 12:26PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered
FolksRunning 11gR2 databases on Sun T4 with broker running
Client primary and physical standby created (db1 and db2)
Primary crashes and db1 database is down...Switches to Standby db2
New Primary db2 is active for a short period of time (less than 1 hour)
Old Primary db1 is started with recovery
Switch back to db1 database and open for transactions...db2 switched to standby mode again
What will happen to entries in original db1 Mlog that were never transported to db2 for apply process.
I am assuming that any redo files need to be physically copied from the file system to db2 and applied before db2 becomes the new primary to maintain consistency
Client primary and physical standby created (db1 and db2)
Primary crashes and db1 database is down...Switches to Standby db2
New Primary db2 is active for a short period of time (less than 1 hour)
Old Primary db1 is started with recovery
Switch back to db1 database and open for transactions...db2 switched to standby mode again
What will happen to entries in original db1 Mlog that were never transported to db2 for apply process.
I am assuming that any redo files need to be physically copied from the file system to db2 and applied before db2 becomes the new primary to maintain consistency
0