How Does this work in Detail: Archiving the Standby Redo Log on the Standby Database
edited Oct 23, 2009 5:26AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
This is mainly just for my interest.
LGWR ASYNC on a physical standby 10gR2
The documentation says the following:
A log switch on the primary database triggers a log switch on the standby database, causing ARCn processes on the standby database to archive the standby redo log files to archived redo log files on the standby database.
So what process on the primary sends the message to what process on the standby telling the ARCH on the standby server to archive the current standby redo log?
Does the ARCH process on the primary send a message to the RFS process on the standby server, and then the RFS process sends a message to the ARCH process on the standby server telling the standby server ARCH to archive the current standby redo log?
LGWR ASYNC on a physical standby 10gR2
The documentation says the following:
A log switch on the primary database triggers a log switch on the standby database, causing ARCn processes on the standby database to archive the standby redo log files to archived redo log files on the standby database.
So what process on the primary sends the message to what process on the standby telling the ARCH on the standby server to archive the current standby redo log?
Does the ARCH process on the primary send a message to the RFS process on the standby server, and then the RFS process sends a message to the ARCH process on the standby server telling the standby server ARCH to archive the current standby redo log?
0