官术网_书友最值得收藏!

Time for action – configuring standby redo logs on primary

Run the following procedures on the primary database to create standby redo logfiles:

  1. Check the ORL's members and the sizes of each member as follows:
    SQL> select a.group#, a.status, a.bytes/1024/1024 SizeMB, b.member from v$log a, v$logfile b where a.group#=b.group# order by group#;
    
    GROUP# STATUS SizeMB MEMBER
    ------ -------- ---------- --------------------------------------
     1 INACTIVE 100 /u01/app/oracle/oradata/orcl/redo01.log
     2 CURRENT 100 /u01/app/oracle/oradata/orcl/redo02.log
     3 INACTIVE 100 /u01/app/oracle/oradata/orcl/redo03.log
     4 INACTIVE 100 /u01/app/oracle/oradata/orcl/redo04.log
    
    Tip

    In this single instance of the primary database, we have four redo log groups, each with one member and a size of 100 MB. We should create at least five standby redo log groups.

  2. Add the standby redo logfiles as shown in the following example:
    SQL> alter database add standby logfile group 11 ('/u01/app/oracle/oradata/orcl/standby_redo01.log') size 100m;
    SQL> alter database add standby logfile group 12 ('/u01/app/oracle/oradata/orcl/standby_redo02.log') size 100m;
    SQL> alter database add standby logfile group 13 ('/u01/app/oracle/oradata/orcl/standby_redo03.log') size 100m;
    SQL> alter database add standby logfile group 14 ('/u01/app/oracle/oradata/orcl/standby_redo04.log') size 100m;
    SQL> alter database add standby logfile group 15 ('/u01/app/oracle/oradata/orcl/standby_redo05.log') size 100m;
    
  3. Check the status of new the standby redo logfiles:
    SQL> select group#,bytes,status from v$standby_log;
    GROUP# BYTES STATUS
    ------ --------- ----------
    11 104857600 UNASSIGNED
    12 104857600 UNASSIGNED
    13 104857600 UNASSIGNED
    14 104857600 UNASSIGNED
    15 104857600 UNASSIGNED
    

What just happened?

We've completed the optional task of creating standby redo logs on the primary database. Again, if the standby redo logs were created on primary, the RMAN duplicate will create them on standby automatically.

Fast recovery area (FRA)

Prior to 11g R2, FRA stood for Flash Recover Area, but since Oracle Database 11g R2, FRA stands for Fast Recovery Area. It's a place on the disk where the database automatically manages naming, retention, and deletion of recovery-related files. FRA can contain control files, online redo logfiles, archived redo logs, flashback logs, and RMAN backups. It's not mandatory but strongly recommended to configure FRA.

In order to enable FRA, you need to set two initialization parameters and you don't need to shut down and restart the database. Note that, in Oracle RAC, these parameters should have the same values across instances and the location must be on shared storage.

主站蜘蛛池模板: 广南县| 卢氏县| 靖江市| 兴和县| 平泉县| 巴彦淖尔市| 卓资县| 安化县| 夏河县| 上蔡县| 陕西省| 丹东市| 民权县| 昆明市| 克拉玛依市| 成武县| 新源县| 鸡泽县| 佛山市| 徐闻县| 尚义县| 东安县| 金阳县| 简阳市| 延长县| 宾川县| 申扎县| 达日县| 宜良县| 临武县| 邹城市| 泉州市| 克东县| 丰城市| 政和县| 广水市| 康保县| 彭山县| 海盐县| 金塔县| 龙南县|