ORA-00322: log 3 of thread 1 is not current copy
使用rman進行recover database的時候出現ORA-00322的錯誤:
重新執行recover database ,成功。
RMAN> recover database;
Starting recover at 21-OCT-14
using channel ORA_DISK_1
starting media recovery
archived log for thread 1 with sequence 2 is already on disk as file /u01/app/archivelog/dest1/1_2_861389770.dbf
archived log for thread 1 with sequence 3 is already on disk as file /u01/app/archivelog/dest1/1_3_861389770.dbf
archived log for thread 1 with sequence 4 is already on disk as file /u01/app/archivelog/dest1/1_4_861389770.dbf
archived log for thread 1 with sequence 5 is already on disk as file /u01/app/archivelog2/dest1/1_5_861389770.dbf
archived log for thread 1 with sequence 6 is already on disk as file /u01/app/archivelog2/dest1/1_6_861389770.dbf
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=1
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area/ORCL/backupset/2014_10_19/o1_mf_annnn_TAG20141019T205525_b491xgmf_.bkp
channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area/ORCL/backupset/2014_10_19/o1_mf_annnn_TAG20141019T205525_b491xgmf_.bkp tag=TAG20141019T205525
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/archivelog/dest2/1_1_861389770.dbf thread=1 sequence=1
archived log file name=/u01/app/archivelog/dest1/1_2_861389770.dbf thread=1 sequence=2
archived log file name=/u01/app/archivelog/dest1/1_3_861389770.dbf thread=1 sequence=3
archived log file name=/u01/app/archivelog/dest1/1_4_861389770.dbf thread=1 sequence=4
archived log file name=/u01/app/archivelog2/dest1/1_5_861389770.dbf thread=1 sequence=5
archived log file name=/u01/app/archivelog2/dest1/1_6_861389770.dbf thread=1 sequence=6
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/21/2014 01:00:49
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/u01/app/archivelog2/dest1/1_6_861389770.dbf'
ORA-00283: recovery session canceled due to errors
ORA-00322: log 3 of thread 1 is not current copy
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/orcl/redo03.log'
解決的辦法是執行如下命令(如果日誌檔案已經歸檔,則將"unarchived"去掉):
SYS@orcl 21-OCT-14>alter database clear unarchived logfile '/u01/app/oracle/oradata/orcl/redo03.log';
Database altered.
解決的辦法是執行如下命令(如果日誌檔案已經歸檔,則將"unarchived"去掉):
SYS@orcl 21-OCT-14>alter database clear unarchived logfile '/u01/app/oracle/oradata/orcl/redo03.log';
Database altered.
重新執行recover database ,成功。
SYS@orcl 21-OCT-14>alter database clear unarchived logfile '/u01/app/oracle/oradata/orcl/redo03.log';
Database altered.
SYS@orcl 21-OCT-14>alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SYS@orcl 21-OCT-14>alter database open resetlogs;
Database altered.
Database altered.
SYS@orcl 21-OCT-14>alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SYS@orcl 21-OCT-14>alter database open resetlogs;
Database altered.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29800581/viewspace-1307255/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-01623: log is current log for thread - cannot dropthread
- Thread 1 cannot allocate new logthread
- Thread 1 cannot allocate new log,Checkpoint not completethread
- ORA-00312: online log 3 thread 1: '/oracle/oradata/hundsun/redo03.log'threadOracle
- alter system archive log current noswitch!!Hive
- Thread 1 cannot allocate new log, sequence NNN 錯誤thread
- redolog threadthread
- alter system archive log current / all / switch logfileHive
- Thread 1 cannot allocate new log 的處理辦法thread
- alter system archive log current和alter system switch logfileHive
- Thread 1 cannot allocate new log Private strand flush not complete 警告thread
- SpringMVC @Transactional的陷井大坑引發No Session found for current threadSpringMVCSessionthread
- alter system switch log file 與 archive log current/all 區別Hive
- ALTER SYSTEM SWITCH LOGFILE ALTER SYSTEM ARCHIVELOG CURRENT 區別Hive
- Oracle DG 出現 RFS[6]: No standby redo logfiles created for thread 1Oraclethread
- ORA-00392: log 15 of thread 1 is being cleared, operation not allowedthread
- 異常資訊解決:Could not obtain transaction-synchronized Session for current threadAIsynchronizedSessionthread
- Could not obtain transaction-synchronized Session for current thread原因及解決方案AIsynchronizedSessionthread
- 錯誤記錄(九)Could not obtain transaction-synchronized Session for current threadAIsynchronizedSessionthread
- alter system switch logfile和alter system archive log current的區別Hive
- alter system switch logfile 和 alter system archive log current 的區別Hive
- Vue, Avoided redundant navigation to current location: "/login".VueIDENavigation
- 【Quest3】copy link
- Copy of a Copy of a Copy
- ORA-00312: online log 5 thread 1:誤刪standby log 日誌組thread
- [轉]alter system switch logfile和alter system archive log current的區別Hive
- zt:alter system switch logfile與ALTER SYSTEM ARCHIVE LOG CURRENT的區別Hive
- PTA第1~3次作業blog
- 用rman copy current controlfile實現控制檔案路徑改變的遷移
- 通過MySQL relaylog + SQL_Thread 增量恢復binlogMySqlthread
- ORA-01511 error in renaming log/data files ORA-00261 log 4 of thread 1 is beingErrorthread
- 1.Monitor Current SQL Running(10g)SQL
- 3 Steps to Perform SSH Login Without Password Using ssh-keygen & ssh-copy-idORM
- 10G/11G/12cr1版本中backup archivelog命令是否會觸發歸檔current logfile操作Hive
- gc current request等待事件,介紹p1,p2,p3轉換方法GC事件
- Digital Current-Mode Control Challenges Analog CounterpartsGit
- 題目集1~3的總結性Blog
- Python3中copy模組常用功能及其他幾種copy方式比較Python