Oracle数据库数据恢复、性能优化

找回密码
注册
搜索
热搜: 活动 交友 discuz
发新帖

999

积分

1

好友

942

主题
1#
发表于 2017-4-13 10:52:39 | 查看: 2127| 回复: 2

环境:用虚拟机搭建的两台服务器组成的ORALCE11.2.0.4.0 RAC环境,都报同样的系统错误:
[oracle@jljcdb1 ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on 星期一 7月 27 14:01:53 2015

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

ERROR:
ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 30: Read-only file system
Additional information: 9925
ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 30: Read-only file system
Additional information: 9925


请输入用户名:  
ERROR:
ORA-01017: 用户名/口令无效; 登录被拒绝


请输入用户名:  
ERROR:
ORA-01017: 用户名/口令无效; 登录被拒绝


SP2-0157: 在 3 次尝试之后无法连接到 ORACLE, 退出 SQL*Plus
[oracle@jljcdb1 ~]$
ORACLE相关的文件都存放在/u01目录下面的:
[root@jljcdb1 /]# df -h
文件系统              容量  已用 可用 已用% 挂载点
/dev/mapper/VolGroup00-LogVol00
                       64Z   64Z  266G 100% /
/dev/mapper/VolGroup00-LogVol02
                       38G  432M   36G   2% /var
/dev/mapper/VolGroup00-LogVol03
                       49G   23G   24G  50% /u01
/dev/sda1             198M   13M  175M   7% /boot
tmpfs                  16G     0   16G   0% /dev/shm
[root@jljcdb1 /]#
于是尝试在/U01目录下面建立个文件试试,也得到同样的错误:
[root@jljcdb1 /]# mkdir /u01/a
mkdir: 无法创建目录 “/u01/a”: 只读文件系统
[root@jljcdb1 /]#
用MOUNT命令查看:
[root@jljcdb1 ~]# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/mapper/VolGroup00-LogVol02 on /var type ext3 (rw)
/dev/mapper/VolGroup00-LogVol03 on /u01 type ext3 (ro)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

mount: warning /etc/mtab is not writable (e.g. read-only filesystem).
       It's possible that information reported by mount(undefined is not
       up to date. For actual information about system mount points
       check the /proc/mounts file.

[root@jljcdb1 ~]#
查看/proc/mount文件:
[root@jljcdb1 ~]# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 ro,data=ordered 0 0
/dev /dev tmpfs rw 0 0
/proc /proc proc rw 0 0
/sys /sys sysfs rw 0 0
/proc/bus/usb /proc/bus/usb usbfs rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/VolGroup00/LogVol02 /var ext3 rw,data=ordered 0 0
/dev/VolGroup00/LogVol03 /u01 ext3 ro,data=ordered 0 0
/dev/sda1 /boot ext3 rw,data=ordered 0 0
tmpfs /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
[root@jljcdb1 ~]#
上面的文件用ROOT用户去修改但报没有权限,不能修改。

接着利用其他网上的说法去尝试,发现仍然不行:
[root@jljcdb1 /]# mount -o remount ,rw -t ext3 /u01
mount: block device ,rw is write-protected, mounting read-only
[root@jljcdb1 /]#
在网上找了一些文章,有的说是文件系统损坏,有的说的磁盘损坏,哪位仁兄遇到过给个解决方法啊!!




下载专业ORACLE数据库恢复工具PRM-DUL  For Oracle http://www.parnassusdata.com/

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!

诗檀软件专业数据库修复团队

服务热线 : 13764045638  QQ: 47079569     邮箱:service@parnassusdata.com
3#
发表于 2017-4-13 10:57:02
root@jljcdb1 /]# cat /var/log/messages
Jul 26 04:02:02 jljcdb1 syslogd 1.4.1: restart.
Jul 27 13:00:33 jljcdb1 kernel: ext3_abort called.
Jul 27 13:00:33 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:02:12 jljcdb1 kernel: ext3_abort called.
Jul 27 13:02:12 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:02:12 jljcdb1 kernel: ext3_abort called.
Jul 27 13:02:12 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:06:03 jljcdb1 kernel: ext3_abort called.
Jul 27 13:06:03 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:06:03 jljcdb1 kernel: ext3_abort called.
Jul 27 13:06:03 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:09:40 jljcdb1 kernel: ext3_abort called.
Jul 27 13:09:40 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:09:40 jljcdb1 kernel: ext3_abort called.
Jul 27 13:09:40 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:10:44 jljcdb1 kernel: ext3_abort called.
Jul 27 13:10:44 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:10:44 jljcdb1 kernel: ext3_abort called.
Jul 27 13:10:44 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:42:53 jljcdb1 kernel: ext3_abort called.
Jul 27 13:42:53 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:42:53 jljcdb1 kernel: ext3_abort called.
Jul 27 13:42:53 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:44:04 jljcdb1 kernel: ext3_abort called.
Jul 27 13:44:04 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:44:04 jljcdb1 kernel: ext3_abort called.
Jul 27 13:44:04 jljcdb1 kernel: EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
Jul 27 13:48:04 jljcdb1 kernel: EXT3-fs error (device dm-0) in ext3_reserve_inode_write: IO failure
Jul 27 13:48:04 jljcdb1 kernel: Aborting journal on device dm-0.
Jul 27 13:48:04 jljcdb1 kernel: EXT3-fs error (device dm-0) in ext3_dirty_inode: IO failure
Jul 27 13:48:04 jljcdb1 kernel: ext3_abort called.
Jul 27 13:48:04 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal
Jul 27 13:48:04 jljcdb1 kernel: Remounting filesystem read-only
Jul 27 13:49:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 13:50:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 13:50:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33556337: inode out of bounds - offset=0, inode=33556337, rec_len=12, name_len=1
Jul 27 13:50:01 jljcdb1 last message repeated 2 times
Jul 27 13:50:25 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33161217: inode out of bounds - offset=0, inode=33161217, rec_len=12, name_len=1
Jul 27 13:50:47 jljcdb1 last message repeated 19 times
Jul 27 13:51:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 13:51:16 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33161261: inode out of bounds - offset=0, inode=33161261, rec_len=12, name_len=1
Jul 27 13:51:20 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33161217: inode out of bounds - offset=0, inode=33161217, rec_len=12, name_len=1
Jul 27 13:51:21 jljcdb1 last message repeated 4 times
Jul 27 13:52:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 13:53:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 13:55:01 jljcdb1 last message repeated 2 times
Jul 27 13:55:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33556337: inode out of bounds - offset=0, inode=33556337, rec_len=12, name_len=1
Jul 27 14:00:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33556337: inode out of bounds - offset=0, inode=33556337, rec_len=12, name_len=1
Jul 27 14:00:01 jljcdb1 last message repeated 2 times
Jul 27 14:01:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:01:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33556337: inode out of bounds - offset=0, inode=33556337, rec_len=12, name_len=1
Jul 27 14:01:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33194232: inode out of bounds - offset=0, inode=33194232, rec_len=12, name_len=1
Jul 27 14:01:01 jljcdb1 last message repeated 2 times
Jul 27 14:01:47 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33556337: inode out of bounds - offset=0, inode=33556337, rec_len=12, name_len=1
Jul 27 14:01:47 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33161261: inode out of bounds - offset=0, inode=33161261, rec_len=12, name_len=1
Jul 27 14:02:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:03:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:05:01 jljcdb1 last message repeated 2 times
Jul 27 14:05:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33556337: inode out of bounds - offset=0, inode=33556337, rec_len=12, name_len=1
Jul 27 14:06:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:07:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:07:20 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_find_entry: bad entry in directory #72679425: inode out of bounds - offset=2404, inode=72679511, rec_len=28, name_len=15
Jul 27 14:07:20 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_find_entry: bad entry in directory #72679425: inode out of bounds - offset=1788, inode=72679519, rec_len=24, name_len=13
Jul 27 14:08:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:09:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:10:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:10:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33556337: inode out of bounds - offset=0, inode=33556337, rec_len=12, name_len=1
Jul 27 14:10:01 jljcdb1 last message repeated 2 times
Jul 27 14:11:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:12:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:14:01 jljcdb1 last message repeated 2 times
Jul 27 14:15:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:15:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33556337: inode out of bounds - offset=0, inode=33556337, rec_len=12, name_len=1
Jul 27 14:16:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:17:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
Jul 27 14:19:01 jljcdb1 last message repeated 2 times
Jul 27 14:20:01 jljcdb1 kernel: EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory

回复 只看该作者 道具 举报

2#
发表于 2017-4-13 10:56:36
附:
[root@jljcdb1 /]#dmesg
EXT3-fs error (device dm-2): ext3_free_blocks: Freeing blocks not in datazone - block = 544042866, count = 1
EXT3-fs error (device dm-2): ext3_free_blocks: Freeing blocks not in datazone - block = 1633906540, count = 1

EXT3-fs error (device dm-2): ext3_free_blocks: Freeing blocks not in datazone - block = 1696607347, count = 1
EXT3-fs error (device dm-2): ext3_free_blocks: Freeing blocks not in datazone - block = 544236654, count = 1
EXT3-fs error (device dm-2) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device dm-2) in ext3_truncate: Journal has aborted
EXT3-fs error (device dm-2) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device dm-2) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device dm-2) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device dm-2) in ext3_delete_inode: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data
ext3_abort called.
EXT3-fs error (device dm-2): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
EXT3-fs error (device dm-0) in ext3_reserve_inode_write: IO failure
Aborting journal on device dm-0.
EXT3-fs error (device dm-0) in ext3_dirty_inode: IO failure
ext3_abort called.
EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-2): ext3_remount: Abort forced by user
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33556337: inode out of bounds - offset=0, inode=33556337, rec_len=12, name_len=1
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #33783818: inode out of bounds - offset=0, inode=33783818, rec_len=12, name_len=1
[root@jljcdb1 /]#

回复 只看该作者 道具 举报

您需要登录后才可以回帖 登录 | 注册

QQ|手机版|Archiver|Oracle数据库数据恢复、性能优化

GMT+8, 2024-12-21 00:50 , Processed in 0.048155 second(s), 21 queries .

Powered by Discuz! X2.5

© 2001-2012 Comsenz Inc.

回顶部
TEL/電話+86 13764045638
Email service@parnassusdata.com
QQ 47079569