From MOS Note 219344.1
How Do I create Standby Redo Logs ??
------------------------------------------------------------
Standby Redo Logs are additional Redo Log Groups. If you were to query the V$LOGFILE view on the Standby Database,
the output would typically look something like this:
SQL> select * from v$logfile;
GROUP# STATUS TYPE MEMBER
------ ------- ------- ------------------------------------
1 ONLINE C:\ORACLE\ORADATA\STANDBY\REDO01.LOG
2 ONLINE C:\ORACLE\ORADATA\STANDBY\REDO02.LOG
3 ONLINE C:\ORACLE\ORADATA\STANDBY\REDO03.LOG
Before you add the Standby Redo Logs to your Standby Database, verify the number of maximum Logfile Groups and Logfile Members.
If you don't remember these values, you can look at the CREATE CONTROLFILE script.
To get such a script, run the following command:
SQL> alter database backup controlfile to trace;
This will create a *.TRC-file in your UDUMP Directory. When you edit or view this newly created file, you will find a script to recreate the Controlfile.
Notice the following relevant entries:
MAXLOGFILES 8
MAXLOGMEMBERS 3
In this example you can create a maximum of eight (8) Logfile groups. Each group can contain a maximum of three (3) Members.
Now we can add Standby Redo Log files to the Standby Database (of course, the Standby Database must be in the MOUNT State):
SQL> alter database add standby logfile group 4 ('C:\ORACLE\ORADATA\STANDBY\STBY04.LOG') SIZE 5M;
You can also add any further members to each group:
SQL> alter database add standby logfile member 'C:\ORACLE\ORADATA\STANDBY\STBY14.LOG' to group 4;
Please keep in mind that if the RFS process is able to write into a Standby Redo Log, the filesize of the Standby Redo Log MUST be equal to the
current Online Redo Log of the Primary Database!!