.
Standby Redo Logs (SRL) : is similar to Online Redo Log (ORL) and only difference between two is that Standby Redo Log is used to store redo data received from another database (primary database).
Standby Redo Logs are only used if you have the LGWR as transport mode to Remote Standby Database. (step to check transport mode below)
.
In what scenarios Standby Redo Logs are required ?
Standby Redo Log is required if
1) Your standby database is in maximum protection or maximum availability modes. (Physical Standby Database can run in one of three modes - Maximum Protection, Maximum Availability and Maximum Performance)
or
2) If you are using Real-Time Apply on Standby Database.
or
3) If you are using Cascaded Destinations
.
Things good to know about SRL
i) Standby Redo Logs should be same size as of Online Redo Logs. (The RFS process will attach Standby Redo Logs only if they are of same size as of Online Redo Log)
ii) Although the standby redo log is only used when the database is running in the standby role, Oracle recommends that you create a standby redo log on the primary database so that the primary database can switch over quickly to the standby role without the need for additional DBA intervention.
iii)Standby redo logs can be created even after the standby has been created. In this case create the SRL’s on the primary before the creation of SRL on the standby database. (Standby Redo Log is not mandatory for Primary Database but its good practice and useful in role conversion from Primary to Standby Database)
iv)It is a best practice/recommendation to maintain Standby Redo Logs (SRLs) on both the standby AND primary database when using LGWR transport mode regardless of protection mode (Maximum Protection/Performance/Availability).
.
Q. What is RFS process on Standby Database ?
RFS - Remote File System on standby database receives data from Primary Database and writes it to Disk.
.
Q. How to identify which transport mode (Archiver or Log Writer) you are using to ship ?
SQL> show parameter log_archive_dest_
log_archive_dest_<n> SERVICE=visr12_standby [ARCH | LGWR]
If neither the ARCH or LGWR attribute is specified, the default is ARCH.
More information about log_archive_dest_<n> here
.
Q. How to check if you are using Real-Time Apply ?
SQL> SELECT DEST_ID, RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS;
Q. How to identify standby redo logs ?
SQL> select * from v$standby_log;
Q. How to see members of standby redo log file
SQL> select * from v$logfile where type=’STANDBY’;
.
Q. How to add Standby Redo Log File Group to a Specific Group Number
SQL> alter database add standby logfile group 4 (
‘/<full_path_for_srl>/log04a.dbf’,
‘/<full_path_for_srl>/log04b.dbf’
) size 50m;
.
References/Related Document
- Online Redo, Archived Redo and Standby Redo Logs
- 219344.1 Usage, Benefits and Limitations of Standby Redo Logs (SRL)
Related Posts for Apps DR
- Oracle Dataguard in Apps 11i E-Business Suite as Disaster Recovery
- Configure Oracle Dataguard
- Oracle Dataguard for Business Continuity
- Configure Oracle Data Guard Part II
- Standby Redo Logs (SRL) in Standby Database
Popularity: 7% [?]







Good hands-on exercises (installation, patching, cloning), very experienced trainer worth for Money 
1 user commented in " Standby Redo Logs (SRL) in Standby Database "
Follow-up comment rss or Leave a TrackbackGreat post. I wanted to let you know that when you build Standby Redo Logs using ASM and db_create_online_log_dest_N Oracle will automatically build TWO SRL. One in FRA and one in a Non-FRA datagroup. Oracle recommends that you remove the second one as you should only have 1 SRL per group and the # of groups should be 1 > current number of groups on your primary.
Thanks.
Leave A Reply