1.RMAN报错。
RMAN在应用部分归档日志之后收到如下报错：
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/13/2014 00:03:03
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/oradata/bak/archivelog/2014_11_12/o1_mf_1_62193_b65oryl5_.arc'
ORA-00283: recovery session canceled due to errors
ORA-19755: could not open change tracking file
ORA-19750: change tracking file: '/u01/app/oracle/block_change_file'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
执行下面的SQL禁用block change tracking，数据库即可继续正常的应用archivelog：
SQL > alter database disable block change tracking;
Database altered.
2.resetlogs之后检查主库和备库的日志同步情况。
?通常在主库执行以下的SQL语句可以用于检查主库和备库日志同步情况：
SQL> select dest_id,thread#,max(sequence#) from v$archived_log where resetlogs_change#=936497858? group by dest_id,thread#;
? DEST_ID? ? THREAD# MAX(SEQUENCE#)
---------- ---------- --------------
? ? ? ? 2? ? ? ? ? 1? ? ? ? ? ? ? 9
? ? ? ? 1? ? ? ? ? 1? ? ? ? ? ? ? 9
? ? 由于主数据库在打开的时候执行了alter database open resetlogs，所以查询v$archived_log要跟上resetlogs_change#，确保查看的是现在数据库的归档情况，resetlogs_change#可以通过v$database.resetlogs_change#获得，另外，由于resetlogs打开了数据库，所以sequence#重新开始计数。
3.对活动的Standby LogFile的处理。
? 停止主数据库之后，我们是想将原来的所有Online Redo Logfile和Standby Logfile都拷贝到新服务器，通过alter databae rename file ... to ...的方式进行重命名，没想到的是Active的Standby Logfile无法进行重命名（收到报错：ORA-01511: error in renaming log/data files），但又必须将Standby Logfile文件放在指定的目录下，下面是查询v$logfile的状态：
SQL> select group#,member from v$logfile;
? ? GROUP#
----------
MEMBER
--------------------------------------------------------------------------------
? ? ? ? 3
/oradata/orcl/REDO03.LOG
? ? ? ? 2
/oradata/orcl/REDO02.LOG
? ? ? ? 1
/oradata/orcl/REDO01.LOG
? ? GROUP#
----------
MEMBER
--------------------------------------------------------------------------------
? ? ? ? 4
/u01/app/oracle/oradata/orcl/sredo01.log
? ? ? ? 5
/oradata/orcl/sredo02.log
? ? ? ? 6
/oradata/orcl/sredo03.log
? ? GROUP#
----------
MEMBER
--------------------------------------------------------------------------------
? ? ? ? 7
/oradata/orcl/sredo04.log
7 rows selected.
group# 4是主数据库之前的Active Standby Logfile，无法对其进行alter database rename file操作。
SQL> alter database drop logfile group 4;
alter database drop logfile group 4
*
ERROR at line 1:
ORA-00315: log 4 of thread 1, wrong thread # 0 in header
ORA-00312: online log 4 thread 1: '/u01/app/oracle/oradata/orcl/sredo01.log'
尝试DROP GROUP组失败。
SQL> alter database add logfile member '/oradata/orcl/sredo01.log' to group 4;
alter database add logfile member '/oradata/orcl/sredo01.log' to group 4
*
ERROR at line 1:
ORA-16161: Cannot mix standby and online redo log file members for group 4
尝试添加成员失败。
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 4;? ?
ALTER DATABASE CLEAR LOGFILE GROUP 4
*
ERROR at line 1:
ORA-00350: log 4 of instance orcl (thread 1) needs to be archived
ORA-00312: online log 4 thread 1: '/u01/app/oracle/oradata/orcl/sredo01.log'
由于未归档所以直接CLEAR失败。
SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 4;
Database altered.
CLEAR UNARCHIVED成功。
?对Standby Logfile的处理办法和对Online Redo Logfile的处理办法一致。
SQL> sel