ORA-00392: log 15 of thread 1 is being cleared, operation not allowed
今天在做recover database後使用alter database open resetlogs開啟資料庫遇到錯誤
描述一下之前的操作步驟
1,還原資料檔案
run{
set newname for datafile 1 to ‘+DATA’;
..
restore database;
switch datafile all;
}
2,恢復資料庫
recover database
修改redo日誌的路徑到ASM
alter database rename file '/sgpmdb/oradata/u01/cmsdb/log13a.log' to '+REDO';
alter database rename file '/sgpmdb/oradata/u01/cmsdb/log13b.log' to '+REDO';
alter database rename file '/sgpmdb/oradata/u01/cmsdb/log14.log' to '+REDO';
..
alter database rename file '/sgpmdb/oradata/u01/cmsdb/log24b.log' to '+REDO’;
3,開啟資料庫庫報錯
alter database open resetlogs;
ORA-00392: log 15 of thread 1 is being cleared, operation not allowed
分析:log 15和log 19分別是生產庫節點一和節點二的當前日誌組,在災備端resetlogs命令後要重新建立redo,但是15、19被記錄為當前狀態current不允許被清除。其實解決方法很簡單,就是採取手工清除。
解決方案:
1,手工清除current組日誌
alter database clear logfile group 15;
alter database clear logfile group 19;
2,開啟資料庫成功
alter database open resetlogs;
下面是掃尾工作,針對此次專案
3,禁用thread 2(源端為RAC,目標為單例項)
alter database disable thread 2;
4,刪除thread 2的日誌組
alter database drop logfile group 19;
..
alter database drop logfile group 24;
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/2317695/viewspace-2056298/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-01511 error in renaming log/data files ORA-00261 log 4 of thread 1 is beingErrorthread
- Thread 1 cannot allocate new logthread
- oracle redo log operationOracle Redo
- Thread 1 cannot allocate new log,Checkpoint not completethread
- ORA-16179: incremental changes to "log_archive_dest_1" not allowed with SPFILEREMHive
- Thread 1 cannot allocate new log, sequence NNN 錯誤thread
- redolog threadthread
- Thread 1 cannot allocate new log 的處理辦法thread
- SQL0668N Operation not allowed for reason code "7" on table XXXSQL
- Log actively being archived by another process問題解決Hive
- Thread 1 cannot allocate new log Private strand flush not complete 警告thread
- ORA-00322: log 3 of thread 1 is not current copythread
- Error: User gpmon is not allowed to login Command CenterError
- Oracle DG 出現 RFS[6]: No standby redo logfiles created for thread 1Oraclethread
- ORA-15028: ASM file '..' not dropped; currently being accessedASM
- sqlnet.log error - Operation timed outSQLError
- Error: User gpmon is not allowed to login Command Center.Error
- SQLNET.ALLOWED_LOGON_VERSION (Doc ID 755605.1)SQLGo
- zblog顯示Allowed memory size of 6553652 bytes exhauste
- ORA-00312: online log 5 thread 1:誤刪standby log 日誌組thread
- ORA-00312: online log 3 thread 1: '/oracle/oradata/hundsun/redo03.log'threadOracle
- ORA-01623: log is current log for thread - cannot dropthread
- ValueError: output parameter for reduction operation logical_and has too many dimensions ?Error
- 執行alter database open resetlogs提示ORA-00392和ORA-00312錯誤Database
- 通過MySQL relaylog + SQL_Thread 增量恢復binlogMySqlthread
- 【ASM】ORA-15283: ASM operation requires compatible...ASMUI
- LeetCode-Insert Delete GetRandom O(1) - Duplicates allowedLeetCodedeleterandom
- mysql point in time recovery using sql_thread SQL_Thread增量恢復binlog 要點MySqlthread
- weblogic 1Web
- (RT-Thread學習筆記1)基於 CubeMX 移植 RT-Thread Nanothread筆記NaN
- 深入理解 Nuxt.js 中的 app:error:cleared 鉤子UXJSAPPError
- post 405 method not allowed
- weblogic使用 Pinned-To-Thread 屬性提高效能Webthread
- tidb Error: Operation aborted by user answer '' (cliutil.operation_aborted)TiDBError
- 一個os thread startup、log file sync等待的故障回顧thread
- MYSQL sync_relay_log對I/O thread的影響分析MySqlthread
- /dev/root filesystem full-unable to log into server-This thread has been closeddevServerthread
- Oracle OCP 1Z0-053 Q540(v$asm_operation)OracleASM