redo log 丟失(非歸檔模式,資料庫正常關閉,redo log 被誤刪除!)
資料庫版本:Release 11.2.0.3.0
錯誤描述:資料庫在正常關閉(shutdown immediate)模式下,資料庫redo log被誤刪除。
1,資料庫正常關閉,刪除redo log 檔案。
---------資料庫無法啟動.
SQL> archive log list;
Database log mode No Archive Mode -------------非歸檔模式。
Automatic archival Disabled
Archive destination /u01/app/oracle/product/11.2.0/dbhome_1/dbs/arch
Oldest online log sequence 1
Current log sequence 1
-bash-3.2$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Mon Oct 16 08:39:02 2017
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 941600768 bytes
Fixed Size 1348860 bytes
Variable Size 528485124 bytes
Database Buffers 406847488 bytes
Redo Buffers 4919296 bytes
Database mounted.
ORA-03113: end-of-file on communication channel--------------資料庫啟動失敗!
Process ID: 5103
Session ID: 125 Serial number: 5
=========tail -f alert_PROD1.log -------------log顯示redo檔案丟掉。
ALTER DATABASE OPEN
Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_lgwr_4990.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/PROD1/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_lgwr_4990.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/PROD1/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_ora_5103.trc:
ORA-00313: open failed for members of log group 1 of thread
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/PROD1/redo01.log'
Mon Oct 16 08:39:10 2017
Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_m000_5105.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/PROD1/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
System state dump requested by (instance=1, osid=5103), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_diag_4980.trc
USER (ospid: 5103): terminating the instance due to error 313
Dumping diagnostic data in directory=[cdmp_20171016083911], requested by (instance=1, osid=5103), summary=[abnormal instance termination].
Instance terminated by USER, pid = 5103
解決方法:
進行不完全恢復,然後resetlog方式開啟資料庫。
SQL> recover database until cancel;
Media recovery complete.
SQL> alter database open resetlogs;
Database altered.
log資訊:
ALTER DATABASE RECOVER database until cancel
Media Recovery Start
started logmerger process
Parallel Media Recovery started with 2 slaves
Media Recovery Not Required
Completed: ALTER DATABASE RECOVER database until cancel
alter database open resetlogs
RESETLOGS after complete recovery through change 1105760
Resetting resetlogs activation ID 2082284563 (0x7c1d2413)
Mon Oct 16 08:40:47 2017
Time drift detected. Please check VKTM trace file for more details.
Mon Oct 16 08:40:48 2017
Setting recovery target incarnation to 3
Mon Oct 16 08:40:48 2017
Assigning activation ID 2178882977 (0x81df1da1)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/PROD1/redo01.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Oct 16 08:40:48 2017
SMON: enabling cache recovery
[5294] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:4294618830 end:4294618860 diff:30 (0 seconds)
Dictionary check beginning
Dictionary check complete
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Oct 16 08:40:49 2017
QMNC started with pid=20, OS id=5305
LOGSTDBY: Validating controlfile with logical metadata
LOGSTDBY: Validation complete
Completed: alter database open resetlogs
Mon Oct 16 08:40:49 2017
Starting background process CJQ0
Mon Oct 16 08:40:49 2017
CJQ0 started with pid=21, OS id=5317
錯誤描述:資料庫在正常關閉(shutdown immediate)模式下,資料庫redo log被誤刪除。
1,資料庫正常關閉,刪除redo log 檔案。
---------資料庫無法啟動.
SQL> archive log list;
Database log mode No Archive Mode -------------非歸檔模式。
Automatic archival Disabled
Archive destination /u01/app/oracle/product/11.2.0/dbhome_1/dbs/arch
Oldest online log sequence 1
Current log sequence 1
-bash-3.2$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Mon Oct 16 08:39:02 2017
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 941600768 bytes
Fixed Size 1348860 bytes
Variable Size 528485124 bytes
Database Buffers 406847488 bytes
Redo Buffers 4919296 bytes
Database mounted.
ORA-03113: end-of-file on communication channel--------------資料庫啟動失敗!
Process ID: 5103
Session ID: 125 Serial number: 5
=========tail -f alert_PROD1.log -------------log顯示redo檔案丟掉。
ALTER DATABASE OPEN
Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_lgwr_4990.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/PROD1/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_lgwr_4990.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/PROD1/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_ora_5103.trc:
ORA-00313: open failed for members of log group 1 of thread
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/PROD1/redo01.log'
Mon Oct 16 08:39:10 2017
Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_m000_5105.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/PROD1/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
System state dump requested by (instance=1, osid=5103), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_diag_4980.trc
USER (ospid: 5103): terminating the instance due to error 313
Dumping diagnostic data in directory=[cdmp_20171016083911], requested by (instance=1, osid=5103), summary=[abnormal instance termination].
Instance terminated by USER, pid = 5103
解決方法:
進行不完全恢復,然後resetlog方式開啟資料庫。
SQL> recover database until cancel;
Media recovery complete.
SQL> alter database open resetlogs;
Database altered.
log資訊:
ALTER DATABASE RECOVER database until cancel
Media Recovery Start
started logmerger process
Parallel Media Recovery started with 2 slaves
Media Recovery Not Required
Completed: ALTER DATABASE RECOVER database until cancel
alter database open resetlogs
RESETLOGS after complete recovery through change 1105760
Resetting resetlogs activation ID 2082284563 (0x7c1d2413)
Mon Oct 16 08:40:47 2017
Time drift detected. Please check VKTM trace file for more details.
Mon Oct 16 08:40:48 2017
Setting recovery target incarnation to 3
Mon Oct 16 08:40:48 2017
Assigning activation ID 2178882977 (0x81df1da1)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/PROD1/redo01.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Oct 16 08:40:48 2017
SMON: enabling cache recovery
[5294] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:4294618830 end:4294618860 diff:30 (0 seconds)
Dictionary check beginning
Dictionary check complete
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Oct 16 08:40:49 2017
QMNC started with pid=20, OS id=5305
LOGSTDBY: Validating controlfile with logical metadata
LOGSTDBY: Validation complete
Completed: alter database open resetlogs
Mon Oct 16 08:40:49 2017
Starting background process CJQ0
Mon Oct 16 08:40:49 2017
CJQ0 started with pid=21, OS id=5317
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/20747382/viewspace-2146005/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Redo log檔案被刪除恢復
- 恢復REDO Log丟失的Oracle資料庫Oracle資料庫
- redo log檔案丟失處理措施
- redo log全部刪除後,啟動資料庫資料庫
- 主庫新增redo log或刪除redo log,這些資訊不會同步到備庫
- Standby Redo Log 的設定原則、建立、刪除、檢視、歸檔位置
- 【REDO】刪除REDO LOG重做日誌組後需要手工刪除對應的日誌檔案
- REDO日誌損壞,非歸檔模式資料檔案恢復模式
- Redo Log之一:理解Oracle redo logOracle Redo
- 修改資料庫歸檔模式(ARCHIVELOG/NOARCHIVELOG)資料庫模式Hive
- 非歸檔模式下資料檔案被誤刪的解決方法模式
- slave庫寫redo、binlog不實時丟資料的場景
- 【REDO】重做日誌檔案(redo log files)管理(增,刪,改,查,切)
- archive log 歸檔模式 啟動關閉Hive模式
- Archive Log模式下Redo Log、Check Point和Switch LogHive模式
- 增大redo log檔案大小
- undo log和redo log
- archive log檔案大小與redo log檔案大小關係探究Hive
- Data Guard 環境下 主備庫Redo log 的新增與刪除
- 達夢資料庫:誤刪除 undo/redo 日誌怎麼辦資料庫
- 丟失所有redo log,解決如下zt
- UNDO表空間資料檔案丟失處理(二)正常關閉資料庫資料庫
- 恢復之非歸檔模式下資料庫非正常關閉的備份與恢復模式資料庫
- Oralce資料庫關閉歸檔日誌並且刪除歸檔日誌資料庫
- 非歸檔資料檔案誤刪除解決辦法
- oracle檔案管理之 redo logOracle
- oracle資料庫正常關閉狀態下丟失undo檔案的恢復Oracle資料庫
- MySQL:Redo & binlogMySql
- mysql之 redo logMySql
- oracle redo log operationOracle Redo
- Dataguard環境修改主庫和standby庫online redo log&standby redo log大小
- [Logmnr]使用logminer找回被誤刪的資料
- MySQL中redo log、undo log、binlog關係以及區別MySql
- MySQL的Redo log 以及Bin logMySql
- online redo log 操作 -- 更改RAC資料庫日誌檔案大小資料庫
- 利用rman刪除硬碟上丟失的archivelog硬碟Hive
- 刪除redo所有日誌,資料庫無法啟動資料庫
- Archived Redo Logs歸檔重做日誌介紹及其優點Hive