一旦rhel5.8造成只读文件系统ORA-00354: corrupt redo log block header

Wed Jun 03 03:31:24 CST 2015

Thread 1 advanced to log sequence 396 (LGWR switch)

  Current log# 3 seq# 396 mem# 0: /u01/app/oracle/oradata/orcl/redo03.log

Wed Jun 03 19:05:48 CST 2015

Thread 1 advanced to log sequence 397 (LGWR switch) ----------------->从这个地方能够看出来：sequence 397为current redo log

  Current log# 1 seq# 397 mem# 0: /u01/app/oracle/oradata/orcl/redo01.log

Wed Jun 03 20:44:19 CST 2015

Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_j000_30071.trc:

ORA-07445: exception encountered: core dump [kglats()+106] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []

ORA-01403: no data found

Wed Jun 03 22:00:26 CST 2015

Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_j001_30285.trc:

ORA-07445: exception encountered: core dump [kglhdiv_callback()+79] [SIGSEGV] [Address not mapped to object] [0x0000000D4] [] []

Thu Jun 04 20:28:17 CST 2015

Starting ORACLE instance (normal)

后来数据库实例重新启动（人为重新启动）：

Completed: ALTER DATABASE   MOUNT

Thu Jun 04 20:28:24 CST 2015

ALTER DATABASE OPEN

Thu Jun 04 20:28:24 CST 2015

Beginning crash recovery of 1 threads

 parallel recovery started with 3 processes

Thu Jun 04 20:28:24 CST 2015

Started redo scan

Thu Jun 04 20:28:24 CST 2015

Completed redo scan

 1210 redo blocks read, 287 data blocks need recovery

Thu Jun 04 20:28:25 CST 2015

Started redo application at

 Thread 1: logseq 397, block 660827

Thu Jun 04 20:28:25 CST 2015

Recovery of Online Redo Log: Thread 1 Group 1 Seq 397 Reading mem 0

  Mem# 0: /u01/app/oracle/oradata/orcl/redo01.log

Thu Jun 04 20:28:25 CST 2015

Completed redo application

Thu Jun 04 20:28:29 CST 2015

Completed crash recovery at

 Thread 1: logseq 397, block 662037, scn 1359645

 287 data blocks read, 287 data blocks written, 1210 redo blocks read

Thu Jun 04 20:28:30 CST 2015

LGWR: STARTING ARCH PROCESSES

ARC0 started with pid=19, OS id=3609

Thu Jun 04 20:28:30 CST 2015

ARC0: Archival started

ARC1: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

ARC1 started with pid=20, OS id=3611

Thu Jun 04 20:28:30 CST 2015

Thread 1 advanced to log sequence 398 (thread open) --->已经使用sequence 398，此时，sequence 398为current redo log

Thread 1 opened at log sequence 398

  Current log# 2 seq# 398 mem# 0: /u01/app/oracle/oradata/orcl/redo02.log

Successful open of redo thread 1

Thu Jun 04 20:28:30 CST 2015

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Thu Jun 04 20:28:30 CST 2015

ARC0: Becoming the 'no FAL' ARCH

ARC0: Becoming the 'no SRL' ARCH

Thu Jun 04 20:28:30 CST 2015

SMON: enabling cache recovery

Thu Jun 04 20:28:30 CST 2015

ARC1: Becoming the heartbeat ARCH

Thu Jun 04 20:28:35 CST 2015

ARC0: Log corruption near block 385521 change 1314765 time ?   --->发现redo log 有损坏

Thu Jun 04 20:28:35 CST 2015

Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_arc0_3609.trc:

ORA-00354: corrupt redo log block header --->发现redo log header有损坏

ORA-00353: log corruption near block 385521 change 1314765 time 06/03/2015 19:05:47

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/orcl/redo01.log'

ARC0: All Archive destinations made inactive due to error 354

Thu Jun 04 20:28:35 CST 2015

ARC0: Closing local archive destination LOG_ARCHIVE_DEST_1: '/home/oracle/1_397_880950378.dbf' (error 354)

 (orcl)

Committing creation of archivelog '/home/oracle/1_397_880950378.dbf' (error 354)

Thu Jun 04 20:28:43 CST 2015

Successfully onlined Undo Tablespace 1.

Thu Jun 04 20:28:43 CST 2015

SMON: enabling tx recovery

Thu Jun 04 20:28:45 CST 2015

ARCH: Archival stopped, error occurred. Will continue retrying

Thu Jun 04 20:28:45 CST 2015

ORACLE Instance orcl - Archival Error

Thu Jun 04 20:28:45 CST 2015

Database Characterset is ZHS16GBK

Thu Jun 04 20:28:45 CST 2015

ORA-16038: log 1 sequence# 397 cannot be archived

ORA-00354: corrupt redo log block header

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/orcl/redo01.log'

Thu Jun 04 20:28:45 CST 2015

Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_arc0_3609.trc:

ORA-16038: log 1 sequence# 397 cannot be archived

ORA-00354: corrupt redo log block header

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/orcl/redo01.log'

Opening with internal Resource Manager plan

replication_dependency_tracking turned off (no async multimaster replication found)

Starting background process QMNC

QMNC started with pid=21, OS id=3637

Thu Jun 04 20:28:49 CST 2015

Completed: ALTER DATABASE OPEN ------->db open了。open归open，无法归档的话。业务早晚会hang。

--->此时/u01/app/oracle/oradata/orcl/redo02.log，是sequence 398，是current redo log。

Thread 1 advanced to log sequence 399 (LGWR switch)

  Current log# 3 seq# 399 mem# 0: /u01/app/oracle/oradata/orcl/redo03.log

--->此时/u01/app/oracle/oradata/orcl/redo03.log，是sequence 399，是current redo log。

--->然后，sqlplus中发出了日志切换的语句：alter system switch logfile;

Thread 1 cannot allocate new log, sequence 400---->已经不能进行日志切换，由于sequence 397未被归档，不同意被覆盖，此时db hang住。

All online logs needed archiving

  Current log# 3 seq# 399 mem# 0: /u01/app/oracle/oradata/orcl/redo03.log

  Thu Jun 04 21:28:31 CST 2015

ARC0: Log corruption near block 385521 change 1314765 time ?

Thu Jun 04 21:28:31 CST 2015

Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_arc0_3609.trc:

ORA-00354: corrupt redo log block header

ORA-00353: log corruption near block 385521 change 1314765 time 06/03/2015 19:05:47

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/orcl/redo01.log'

ARC0: All Archive destinations made inactive due to error 354

Thu Jun 04 21:28:31 CST 2015

ARC0: Closing local archive destination LOG_ARCHIVE_DEST_1: '/home/oracle/1_397_880950378.dbf' (error 354)

 (orcl)

ARCH: Archival stopped, error occurred. Will continue retrying

Thu Jun 04 21:28:34 CST 2015

ORACLE Instance orcl - Archival Error

Thu Jun 04 21:28:34 CST 2015

ORA-16038: log 1 sequence# 397 cannot be archived

ORA-00354: corrupt redo log block header

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/orcl/redo01.log'

Thu Jun 04 21:28:34 CST 2015

Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_arc0_3609.trc:

ORA-16038: log 1 sequence# 397 cannot be archived

ORA-00354: corrupt redo log block header

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/orcl/redo01.log'

ARCH: Archival stopped, error occurred. Will continue retrying

Thu Jun 04 21:28:34 CST 2015

ORACLE Instance orcl - Archival Error

Thu Jun 04 21:28:34 CST 2015

ORA-16014: log 1 sequence# 397 not archived, no available destinations

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/orcl/redo01.log'

Thu Jun 04 21:28:34 CST 2015

Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_arc0_3609.trc:

ORA-16014: log 1 sequence# 397 not archived, no available destinations

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/orcl/redo01.log'

启动db到mount状态。进行处理

[oracle@lei1 ~]$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Fri Jun 12 23:14:24 2015

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

Connected to an idle instance.

SQL> startup mount;

ORACLE instance started.

Total System Global Area 2147483648 bytes

Fixed Size                  2097696 bytes

Variable Size             536874464 bytes

Database Buffers         1593835520 bytes

Redo Buffers               14675968 bytes

Database mounted.

SQL> set line 200

SQL> select * from v$log;

    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM

---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ---------

         1          1        397  536870912          1 NO  INACTIVE               1294462 03-JUN-15

         3          1        399  536870912          1 NO  CURRENT                1361682 04-JUN-15

         2          1        398  536870912          1 YES INACTIVE               1359647 04-JUN-15

SQL> alter database clear logfile group 1;

alter database clear logfile group 1

*

ERROR at line 1:

ORA-00350: log 1 of instance orcl (thread 1) needs to be archived

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/orcl/redo01.log'

SQL> alter database clear unarchived logfile group 1;

Database altered.

SQL> select * from v$log;

    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM

---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ---------

         1          1          0  536870912          1 YES UNUSED                 1294462 03-JUN-15

         3          1        399  536870912          1 NO  CURRENT                1361682 04-JUN-15

         2          1        398  536870912          1 YES INACTIVE               1359647 04-JUN-15

SQL> archive log list;

Database log mode              Archive Mode

Automatic archival             Enabled

Archive destination            /home/oracle

Oldest online log sequence     0

Next log sequence to archive   399

Current log sequence           399

SQL>

此时alert日志的输出例如以下：

Fri Jun 12 23:20:27 CST 2015

alter database clear logfile group 1

Fri Jun 12 23:20:27 CST 2015

ORA-350 signalled during: alter database clear logfile group 1...

Fri Jun 12 23:22:30 CST 2015

alter database clear unarchived logfile group 1

Fri Jun 12 23:22:31 CST 2015

WARNING! CLEARING REDO LOG WHICH HAS NOT BEEN ARCHIVED. BACKUPS TAKEN

    BEFORE 06/04/2015 20:28:30 (CHANGE 1359647) CANNOT BE USED FOR RECOVERY.

Clearing online log 1 of thread 1 sequence number 397

Fri Jun 12 23:22:43 CST 2015

Completed: alter database clear unarchived logfile group 1

一旦rhel5.8造成只读文件系统ORA-00354: corrupt redo log block header的更多相关文章

解决ntfs格式的移动硬盘mount到Linux下时变成只读文件系统的问题
环境介绍主机: XP 虚拟机:VirtualBox+Debian6 遇到的问题我有一块西部数据的移动硬盘,虚拟机中有一些资料需要拷贝到移动硬盘中,然后我将移动硬盘插上后,执行如下设置,将移动硬盘分 ...
Linux文件系统，ntfs分区显示只读文件系统，提示超级快损坏
背景:某天当我打开自己的设备,突然发现ntfs分区无法写入任何文件,提示为只读文件系统,具体现象如下: 修复过程:排除权限问题,使用fsck进行修复无果后,使用e2fsck进行修复显示超级快损坏,这 ...
Ubuntu下U盘只读文件系统，图标上锁，提示无法修改
资料来源于网络,自己总结问题 Ubuntu下有时候插入U盘,发现不能修改其中的内容.例如不能新建文件和文件夹,不能向U盘中复制文件等,系统提示:只读文件系统. 原因大概是U盘的文件系统信息出错(保存 ...
kubernetes高级之创建只读文件系统以及只读asp.net core容器
系列目录使用docker创建只读文件系统容器化部署对应用的运维带来了极大的方便,同时也带来一些新的安全问题需要考虑.比如黑客入侵到容器内,对容器内的系统级别或者应用级别文件进行修改,会造成难以估量 ...
mkdir: 无法创建目录"kk": 只读文件系统
创建文件提示 root@hap1:/test>mkdir kk mkdir: 无法创建目录"kk": 只读文件系统 root@hap1:/test>mount .... ...
linux下U盘变成只读文件系统的修复
问题描述: U盘插入linux下后变成了只读文件系统,不能再往u盘里拷贝文件. 总结:产生这个问题的原因可能是u盘文件系统损坏,操作系统为了防止它损坏系统,将它设置成了只读修复方法: 在window ...
复制”链接文件“到虚拟机（VirtualBox）的”共享文件夹“时报错：创建符号链接时报错：只读文件系统
问题描述: 1.Ubuntu 中的 /www/目录,是宿主主机 Windows 7 以“共享文件夹”的形式挂载的: 2./etc/php.ini 是 /opt/software/php/etc/php ...
linux只读文件系统
一般方法如下首先试下重新挂载行不行 mount -o remount,rw /dev/sda3 不行的话用fsck,具体方法如下 1. mount命令查看变成只读文件的位置,比如/dev/sda32 ...
如何删除/mnt/cdrom?|如何删除只读文件系统（Read-only files ystem）？ failed !bh ? 挂载光盘？挂载usb？
root权限下 : 首先用umount /mnt/文件夹卸载文件系统,必要时可以用umount -f(可能丢失数据)然后rm -rf /mnt/cdrom mkdir /mnt/cdrom moun ...

随机推荐

POJ 2417 Discrete Logging 离散对数
链接:http://poj.org/problem?id=2417 题意: 思路:求离散对数,Baby Step Giant Step算法基本应用. 下面转载自:AekdyCoin [普通Baby S ...
【Python项目】配合爱漫画爬取漫画脚本而设计的GUI漫画阅读器（一）
博客园的第一个坑,想想都有点小激动 =3= 首先是那个爬虫的地址: [原创]最近写的一个比较hack的小爬虫选择工具: 以前用过Qt,那么选pyqt4也就是情理之中了. 明确需求: 0.首先,要读取 ...
HDU 1695 GCD 欧拉函数+容斥原理+质因数分解
链接:http://acm.hdu.edu.cn/showproblem.php?pid=1695 题意:在[a,b]中的x,在[c,d]中的y,求x与y的最大公约数为k的组合有多少.(a=1, a ...
Android动画之二：View Animation
作为一个博客<Android其中的动画:Drawable Animation>.android动画主要分为三大部分.上一篇博客已经解说Drawable Animation的使用方法,即逐帧 ...
顺序容器的insert使用方法
#include <iostream> #include <algorithm> #include <vector> #include <string> ...
[WebGL入门]二十四，补色着色
注:文章译自http://wgld.org/,原作者杉本雅広(doxas),文章中假设有我的额外说明,我会加上［lufy:］,另外,鄙人webgl研究还不够深入,一些专业词语,假设翻译有误,欢迎大家指 ...
乐在其中设计模式(C#) - 解释器模式(Interpreter Pattern)
原文:乐在其中设计模式(C#) - 解释器模式(Interpreter Pattern) [索引页][源码下载] 乐在其中设计模式(C#) - 解释器模式(Interpreter Pattern) 作 ...
JFileChooser
http://www.cnblogs.com/dyllove98/archive/2012/03/05/2461895.html package swing.choose; import java.a ...
Spark SQL 源代码分析系列
从决定写Spark SQL文章的源代码分析,到现在一个月的时间,一个又一个几乎相同的结束很快,在这里也做了一个综合指数,方便阅读,下面是读取顺序 :) 第一章 Spark SQL源代码分析之核心流程 ...
shell script 入门笔记
shell script 入门在 shell script 注意必须使用完全相同写在下面: 1. 指令的运行是从上而下.从左而右的分析与运行: 2. 指令的运行就如同第五章内提到的: 指令.选项 ...

一旦rhel5.8造成只读文件系统ORA-00354: corrupt redo log block header

一旦rhel5.8造成只读文件系统ORA-00354: corrupt redo log block header的更多相关文章

随机推荐

热门专题