ORA-00262: current log 1 of closed thread 1 cannot switch
ORA-00312: online log 1 thread 1:
'/oracle/oradata/LUDA/onlinelog/o1_mf_1_6zlkxrqf_.log'
ORA-00312: online log 1 thread 1:
'/oracle/flash_recovery_area/LUDA/onlinelog/o1_mf_1_6zlky0b9_.log'
ORA-00350: log 2 of instance luda (thread 1) needs to be archived
ORA-00312: online log 2 thread 1:
'/oracle/oradata/LUDA/onlinelog/o1_mf_2_6zlky76o_.log'
ORA-00312: online log 2 thread 1:
'/oracle/flash_recovery_area/LUDA/onlinelog/o1_mf_2_6zlkyghs_.log'
SQL> select GROUP#,ARCHIVED ,STATUS from v$log;
GROUP# ARC STATUS
———- — —————-
1 NO CURRENT
3 NO INACTIVE
2 NO INACTIVE
配置DG时候强行关闭节点2，节点1
再次启动节点一时候报错
[oracle@dg1 09:50:38|~]oerr ora 262
00262, 00000, "current log %s of closed thread %s cannot switch"
// *Cause: The log cannot be cleared or manually archived because it is
// the current log of a closed thread, and it is not possible to
// switch logs so another log is current. All other logs for the
// thread need to be archived, or cleared, and cannot be reused.
// *Action: Archive another log in the same thread first, or complete the
// clearing. See attached errors for the reason the switch cannot
// be completed.
[oracle@dg1 09:59:25|~]oerr ora 312
00312, 00000, "online log %s thread %s: '%s'"
// *Cause: This message reports the filename for details of another message.
// *Action: Other messages will accompany this message. See the
// associated messages for the appropriate action to take.
[oracle@dg1 09:59:30|~]oerr ora 350
00350, 00000, "log %s of instance %s (thread %s) needs to be archived"
// *Cause: The command cannot be done because the log has not been archived,
// and media recovery has been enabled.
// *Action: Archive the log or disable media recovery. If the command supports
// an UNARCHIVED option then it can be used. However this may result
// in making backups unuseable, and forcing the drop of some offline
// files.
这里报2个日志组，快速解决办法：
alter database clear unarchived logfile group 2;
alter database clear unarchived logfile group 1;
alter database open；
当然这个报错的原因是首先关闭了dg2节点，当关闭节点1时候，rfs归档无法找到standby，从而传输失败，报错
clear =。= 不是很妥当的办法。
