Oracle重做日志文件版本不一致问题处理
早上在启动测试数据库时,发现如下问题:数据库版本是11.2.0.3SQLgt; startupOracle instance started. Total System Global Ar
早上在启动测试数据库时,发现如下问题:
数据库版本是11.2.0.3
SQL> startup
Oracle instance started.
Total System Global Area 1653518336 bytes
Fixed Size 2228904 bytes
Variable Size 1140854104 bytes
Database Buffers 503316480 bytes
Redo Buffers 7118848 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 8264
Session ID: 191 Serial number: 3
检查告警日志文件信息如下:
Fri Aug 24 09:52:27 2012
Completed: ALTER DATABASE MOUNT
Fri Aug 24 09:52:27 2012
ALTER DATABASE OPEN
Fri Aug 24 09:52:33 2012
Errors in file /u01/app/oracle/diag/rdbms/enmot2/enmot2/trace/enmot2_lgwr_8222.trc:
ORA-00322: log 2 of thread 1 is not current copy
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02b.log'
ORA-00322: log 2 of thread 1 is not current copy
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02a.log'
Errors in file /u01/app/oracle/diag/rdbms/enmot2/enmot2/trace/enmot2_lgwr_8222.trc:
ORA-00322: log 2 of thread 1 is not current copy
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02b.log'
ORA-00322: log 2 of thread 1 is not current copy
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02a.log'
Errors in file /u01/app/oracle/diag/rdbms/enmot2/enmot2/trace/enmot2_ora_8264.trc:
ORA-00322: log 1 of thread is not current copy
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02a.log'
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/enmot2/redo02b.log'
USER (ospid: 8264): terminating the instance due to error 322
Fri Aug 24 09:52:34 2012
System state dump requested by (instance=1, osid=8264), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/enmot2/enmot2/trace/enmot2_diag_8212.trc
Dumping diagnostic data in directory=[cdmp_20120824095234], requested by (instance=1, osid=8264), summary=[abnormal instance termination].
Instance terminated by USER, pid = 8264
问题比较明显,日志镜像存在问题,由于测试库可以通过resetlog方式打开:
SQL> alter system set "_allow_resetlogs_corruption"=true scope=spfile;
System altered.
SQL> startup mount
ORACLE instance started.
Total System Global Area 1653518336 bytes
Fixed Size 2228904 bytes
Variable Size 1140854104 bytes
Database Buffers 503316480 bytes
Redo Buffers 7118848 bytes
Database mounted.
SQL> recover database until cancel;
Media recovery complete.
SQL> alter database open resetlogs;
Database altered.
此时告警日志信息如下:
Fri Aug 24 09:53:56 2012
alter database open resetlogs
ORA-1139 signalled during: alter database open resetlogs...
Fri Aug 24 09:54:27 2012
ALTER DATABASE RECOVER database until cancel
Media Recovery Start
started logmerger process
Parallel Media Recovery started with 4 slaves
Media Recovery Not Required
Completed: ALTER DATABASE RECOVER database until cancel
alter database open resetlogs
RESETLOGS is being done without consistancy checks. This may result
in a corrupted database. The database should be recreated.
RESETLOGS after incomplete recovery UNTIL CHANGE 1427077
Resetting resetlogs activation ID 1296798128 (0x4d4b91b0)
Fri Aug 24 09:56:11 2012
Setting recovery target incarnation to 2
Fri Aug 24 09:56:12 2012
Assigning activation ID 1297978010 (0x4d5d929a)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/enmot2/redo01a.log
Current log# 1 seq# 1 mem# 1: /u01/app/oracle/oradata/enmot2/redo01b.log
Successful open of redo thread 1
Fri Aug 24 09:56:15 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Aug 24 09:56:15 2012
SMON: enabling cache recovery
[8371] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:68627054 end:68628914 diff:1860 (18 seconds)
Dictionary check beginning
Fri Aug 24 09:56:26 2012
Dictionary check complete
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
Fri Aug 24 09:56:26 2012
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Fri Aug 24 09:56:36 2012
QMNC started with pid=20, OS id=8383
LOGSTDBY: Validating controlfile with logical metadata
Fri Aug 24 09:56:37 2012
LOGSTDBY: Validation complete
Fri Aug 24 09:56:47 2012
Completed: alter database open resetlogs
以上就是整个处理过程。

熱AI工具

Undresser.AI Undress
人工智慧驅動的應用程序,用於創建逼真的裸體照片

AI Clothes Remover
用於從照片中去除衣服的線上人工智慧工具。

Undress AI Tool
免費脫衣圖片

Clothoff.io
AI脫衣器

Video Face Swap
使用我們完全免費的人工智慧換臉工具,輕鬆在任何影片中換臉!

熱門文章

熱工具

記事本++7.3.1
好用且免費的程式碼編輯器

SublimeText3漢化版
中文版,非常好用

禪工作室 13.0.1
強大的PHP整合開發環境

Dreamweaver CS6
視覺化網頁開發工具

SublimeText3 Mac版
神級程式碼編輯軟體(SublimeText3)

MySQL在Web應用中的主要作用是存儲和管理數據。 1.MySQL高效處理用戶信息、產品目錄和交易記錄等數據。 2.通過SQL查詢,開發者能從數據庫提取信息生成動態內容。 3.MySQL基於客戶端-服務器模型工作,確保查詢速度可接受。

InnoDB使用redologs和undologs確保數據一致性和可靠性。 1.redologs記錄數據頁修改,確保崩潰恢復和事務持久性。 2.undologs記錄數據原始值,支持事務回滾和MVCC。

MySQL与其他编程语言相比,主要用于存储和管理数据,而其他语言如Python、Java、C 则用于逻辑处理和应用开发。MySQL以其高性能、可扩展性和跨平台支持著称,适合数据管理需求,而其他语言在各自领域如数据分析、企业应用和系统编程中各有优势。

MySQL索引基数对查询性能有显著影响:1.高基数索引能更有效地缩小数据范围,提高查询效率;2.低基数索引可能导致全表扫描,降低查询性能;3.在联合索引中,应将高基数列放在前面以优化查询。

MySQL的基本操作包括創建數據庫、表格,及使用SQL進行數據的CRUD操作。 1.創建數據庫:CREATEDATABASEmy_first_db;2.創建表格:CREATETABLEbooks(idINTAUTO_INCREMENTPRIMARYKEY,titleVARCHAR(100)NOTNULL,authorVARCHAR(100)NOTNULL,published_yearINT);3.插入數據:INSERTINTObooks(title,author,published_year)VA

MySQL適合Web應用和內容管理系統,因其開源、高性能和易用性而受歡迎。 1)與PostgreSQL相比,MySQL在簡單查詢和高並發讀操作上表現更好。 2)相較Oracle,MySQL因開源和低成本更受中小企業青睞。 3)對比MicrosoftSQLServer,MySQL更適合跨平台應用。 4)與MongoDB不同,MySQL更適用於結構化數據和事務處理。

InnoDBBufferPool通過緩存數據和索引頁來減少磁盤I/O,提升數據庫性能。其工作原理包括:1.數據讀取:從BufferPool中讀取數據;2.數據寫入:修改數據後寫入BufferPool並定期刷新到磁盤;3.緩存管理:使用LRU算法管理緩存頁;4.預讀機制:提前加載相鄰數據頁。通過調整BufferPool大小和使用多個實例,可以優化數據庫性能。

MySQL通過表結構和SQL查詢高效管理結構化數據,並通過外鍵實現表間關係。 1.創建表時定義數據格式和類型。 2.使用外鍵建立表間關係。 3.通過索引和查詢優化提高性能。 4.定期備份和監控數據庫確保數據安全和性能優化。
