4 UNASSIGNED 0 YES UNASSIGNED
5 UNASSIGNED 0 YES UNASSIGNED
6 UNASSIGNED 0 YES UNASSIGNED
从实验情况看：在Primary端，我们进行standby redo log的管理是比较方便的。没有过多的限制。
3、Standby端Standby Redo Log维护
当前Primary端的Online Redo Log情况。
SQL> select group#, sequence#, bytes, status from v$log;
GROUP# SEQUENCE# BYTES STATUS
---------- ---------- ---------- ----------------
1 32 104857600 INACTIVE
2 34 52428800 INACTIVE
3 35 52428800 CURRENT
7 33 10485760 INACTIVE
此时，standby端的standby redo log情况如下：
SQL> select group#, sequence#, dbid,status from v$standby_log;
GROUP# SEQUENCE# DBID STATUS
---------- ---------- -------------------- ----------
4 35 4239941846 ACTIVE
5 0 UNASSIGNED UNASSIGNED
6 0 UNASSIGNED UNASSIGNED
standby redo log对应的是当前Primary的online current redo log。反映在sequence#相同。我们尝试直接添加standby日志。
SQL> alter database add standby logfile group 8 size 100m;
alter database add standby logfile group 8 size 100m
ORA-01156: 进行中的恢复或闪回可能需要访问文件
当前standby处在apply过程，终止apply动作。
SQL> alter database recover managed standby database cancel;
Database altered
SQL> alter database add standby logfile group 8 size 100m;
Database altered
standby redo log日志情况。
SQL> select group#, dbid, sequence#, archived, status from v$standby_log;
GROUP# DBID SEQUENCE# ARCHIVED STATUS
---------- -------------------- ---------- -------- ----------
4 4239941846 35 YES ACTIVE
5 UNASSIGNED 0 NO UNASSIGNED
6 UNASSIGNED 0 NO UNASSIGNED
8 UNASSIGNED 0 YES UNASSIGNED
之后可以启动redo apply过程。
SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered