clause is required only if you want to add one or more standby redo log filegroups to a
primary database thread. If you do not include the
clause andthe configuration uses Real Application Clusters (RAC), Data Guard will automaticallyassign standby redo log file groups to threads at runtime as they are needed by thevarious RAC instances.
Example 3-2 Adding a Standby Redo Log File Group to a Specific Group Number
You can also specify a number that identifies the group using the
SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 102> ('/oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500M;
Using group numbers can make administering standby redo log file groups easier.However, the group number must be between 1 and the value of the
clause.Do not skip log file group numbers (that is, do not number groups 10, 20, 30, and soon), or you will use additional space in the standby database control file.
Although the standby redo log is only used when the database is running in the standbyrole, Oracle recommends that you create a standby redo log on the primary databaseso that the primary database can switch over quickly to the standby role without theneed for additional DBA intervention. Consider using Oracle Enterprise Manager toautomatically configure standby redo log on both your primary and standby databases.
Step 5 Verify the standby redo log file groups were created.
To verify the standby redo log file groups are created and running correctly, invoke alog switch on the primary database, and then query either the
view on the standby database once it has been created. For example:
SQL> SELECT GROUP#,THREAD#,SEQUENCE#,ARCHIVED,STATUS FROM V$STANDBY_LOG;GROUP# THREAD# SEQUENCE# ARC STATUS---------- ---------- ---------- --- ----------3 1 16 NO ACTIVE4 0 0 YES UNASSIGNED5 0 0 YES UNASSIGNED
3.1.4 Set Primary Database Initialization Parameters
On the primary database, you define initialization parameters that control redotransport services while the database is in the primary role. There are additional