oracle 数据库假死，ping不通了，系统日志报错如下，这种情况是如何造成的
oracle 数据库假死，ping不通了，系统日志报错如下，这种情况是怎么造成的？
1，这是linux的message日志：
Mar 29 01:00:49 localhost kernel: EXT4-fs error (device sdb): ext4_ext_map_blocks:3447: inode #17827500: comm oracle: bad extent address lblock: 512, depth: 1 pblock 0
Mar 29 01:00:49 localhost kernel: EXT4-fs error (device sdb): ext4_ext_map_blocks:3447: inode #17827500: comm oracle: bad extent address lblock: 768, depth: 1 pblock 0
Mar 29 01:00:49 localhost kernel: EXT4-fs error (device sdb): ext4_ext_map_blocks:3447: inode #17827500: comm oracle: bad extent address lblock: 768, depth: 1 pblock 0
Mar 29 01:00:51 localhost iscsid: connect to 10.10.0.22:3260 failed (No route to host)
Mar 29 01:00:57 localhost iscsid: connect to 10.10.0.22:3260 failed (No route to host)
Mar 29 01:01:03 localhost iscsid: connect to 10.10.0.22:3260 failed (No route to host)
Mar 29 01:01:09 localhost iscsid: connect to 10.10.0.22:3260 failed (No route to host)
Mar 29 09:21:45 localhost kernel: imklog 5.8.10, log source = /proc/kmsg started.
Mar 29 09:21:45 localhost rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1779" x-info="http://www.rsyslog.com"] start
Mar 29 09:21:45 localhost kernel: Initializing cgroup subsys cpuset
Mar 29 09:21:45 localhost kernel: Initializing cgroup subsys cpu
Mar 29 09:21:45 localhost kernel: BIOS-provided physical RAM map:
2，这是oracle的alert.log日志：
Sun Mar 29 01:00:02 2015
ALTER SYSTEM ARCHIVE LOG
Sun Mar 29 01:00:03 2015
LGWR: Standby redo logfile selected to archive thread 1 sequence 31004
LGWR: Standby redo logfile selected for thread 1 sequence 31004 for destination LOG_ARCHIVE_DEST_2
Thread 1 advanced to log sequence 31004 (LGWR switch)
Current log# 2 seq# 31004 mem# 0: /home/oradata/powerdes/redo02.log
Archived Log entry 60900 added for thread 1 sequence 31003 ID 0xca2ab4eb dest 1:
Sun Mar 29 09:27:42 2015
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =168
LICENSE_MAX_USERS = 0
SYS auditing is enabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options.
Using parameter settings in server-side spfile /oracle/app/oracle/product/11.2.0/dbhome_1/dbs/spfilepowerdes.ora
System parameters with non-default values:
processes = 1000
sessions = 1536
memory_target = 10880M
control_files = "/home/oradata/powerdes/control01.ctl"
------解决思路----------------------
先解决系统问题，再分析数据库
------解决思路----------------------
感觉你的系统磁盘是使用了ext4文件系统的no journal模式,
现在Inode数据有丢失，可以用fsck 对报错的分区 进行一下修复(有可能不能恢复，这个命令是不可逆的)
1，这是linux的message日志：
Mar 29 01:00:49 localhost kernel: EXT4-fs error (device sdb): ext4_ext_map_blocks:3447: inode #17827500: comm oracle: bad extent address lblock: 512, depth: 1 pblock 0
Mar 29 01:00:49 localhost kernel: EXT4-fs error (device sdb): ext4_ext_map_blocks:3447: inode #17827500: comm oracle: bad extent address lblock: 768, depth: 1 pblock 0
Mar 29 01:00:49 localhost kernel: EXT4-fs error (device sdb): ext4_ext_map_blocks:3447: inode #17827500: comm oracle: bad extent address lblock: 768, depth: 1 pblock 0
Mar 29 01:00:51 localhost iscsid: connect to 10.10.0.22:3260 failed (No route to host)
Mar 29 01:00:57 localhost iscsid: connect to 10.10.0.22:3260 failed (No route to host)
Mar 29 01:01:03 localhost iscsid: connect to 10.10.0.22:3260 failed (No route to host)
Mar 29 01:01:09 localhost iscsid: connect to 10.10.0.22:3260 failed (No route to host)
Mar 29 09:21:45 localhost kernel: imklog 5.8.10, log source = /proc/kmsg started.
Mar 29 09:21:45 localhost rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1779" x-info="http://www.rsyslog.com"] start
Mar 29 09:21:45 localhost kernel: Initializing cgroup subsys cpuset
Mar 29 09:21:45 localhost kernel: Initializing cgroup subsys cpu
Mar 29 09:21:45 localhost kernel: BIOS-provided physical RAM map:
2，这是oracle的alert.log日志：
Sun Mar 29 01:00:02 2015
ALTER SYSTEM ARCHIVE LOG
Sun Mar 29 01:00:03 2015
LGWR: Standby redo logfile selected to archive thread 1 sequence 31004
LGWR: Standby redo logfile selected for thread 1 sequence 31004 for destination LOG_ARCHIVE_DEST_2
Thread 1 advanced to log sequence 31004 (LGWR switch)
Current log# 2 seq# 31004 mem# 0: /home/oradata/powerdes/redo02.log
Archived Log entry 60900 added for thread 1 sequence 31003 ID 0xca2ab4eb dest 1:
Sun Mar 29 09:27:42 2015
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =168
LICENSE_MAX_USERS = 0
SYS auditing is enabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options.
Using parameter settings in server-side spfile /oracle/app/oracle/product/11.2.0/dbhome_1/dbs/spfilepowerdes.ora
System parameters with non-default values:
processes = 1000
sessions = 1536
memory_target = 10880M
control_files = "/home/oradata/powerdes/control01.ctl"
------解决思路----------------------
先解决系统问题，再分析数据库
------解决思路----------------------
感觉你的系统磁盘是使用了ext4文件系统的no journal模式,
现在Inode数据有丢失，可以用fsck 对报错的分区 进行一下修复(有可能不能恢复，这个命令是不可逆的)