紧急求助：出现很多坏块，无法全备，如何解决？
平台：solaris9
oracle9208数据库
日志报错信息如下：
Wed Dec 26 01:27:42 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 3
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.8.0.
System parameters with non-default values:
processes = 300
timed_statistics = TRUE
shared_pool_size = 1610612736
sga_max_size = 7535044816
large_pool_size = 33554432
java_pool_size = 67108864
control_files = /opt/oracle/oradata/BIMS/control01.ctl, /opt/oracle/oradata/BIMS/control02.ctl, /opt/oracle/oradata/BIM
S/control03.ctl
db_block_size = 8192
db_cache_size = 4294967296
compatible = 9.2.0.0.0
log_archive_start = TRUE
log_archive_dest = /archive
db_file_multiblock_read_count= 16
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = BIMS
dispatchers = (PROTOCOL=TCP) (SERVICE=BIMSXDB)
job_queue_processes = 10
hash_join_enabled = TRUE
background_dump_dest = /opt/oracle/admin/BIMS/bdump
user_dump_dest = /opt/oracle/admin/BIMS/udump
core_dump_dest = /opt/oracle/admin/BIMS/cdump
sort_area_size = 524288
db_name = BIMS
open_cursors = 300
star_transformation_enabled= FALSE
query_rewrite_enabled = FALSE
pga_aggregate_target = 805306368
aq_tm_processes = 1
PMON started with pid=2, OS id=12439
DBW0 started with pid=3, OS id=12441
LGWR started with pid=4, OS id=12443
CKPT started with pid=5, OS id=12445
SMON started with pid=6, OS id=12447
RECO started with pid=7, OS id=12449
CJQ0 started with pid=8, OS id=12451
QMN0 started with pid=9, OS id=12453
Wed Dec 26 01:27:45 2007
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=12, OS id=12459
ARC0: Archival started
ARC1 started with pid=13, OS id=12461
ARC1: Archival started
Wed Dec 26 01:27:45 2007
ARCH: STARTING ARCH PROCESSES COMPLETE
Wed Dec 26 01:27:45 2007
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no FAL' ARCHARC1: Thread not mounted
Wed Dec 26 01:27:45 2007
ARC0: Becoming the heartbeat ARCH
ARC0: Becoming the heartbeat ARCHARC0: Thread not mounted
Wed Dec 26 01:27:49 2007
ALTER DATABASE MOUNT
Wed Dec 26 01:27:53 2007
Successful mount of redo thread 1, with mount id 2034336085
Wed Dec 26 01:27:53 2007
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Wed Dec 26 01:27:53 2007
ALTER DATABASE OPEN
Wed Dec 26 01:27:53 2007
LGWR: Primary database is in CLUSTER CONSISTENT mode
Thread 1 opened at log sequence 83
Current log# 2 seq# 83 mem# 0: /opt/oracle/oradata/BIMS/redo02.log
Successful open of redo thread 1
Wed Dec 26 01:27:53 2007
SMON: enabling cache recovery
Wed Dec 26 01:27:53 2007
Successfully onlined Undo Tablespace 1.
Wed Dec 26 01:27:53 2007
SMON: enabling tx recovery
Wed Dec 26 01:27:53 2007
Database Characterset is ZHS16GBK
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: ALTER DATABASE OPEN
Wed Dec 26 01:32:01 2007
Hex dump of Absolute File 26, Block 451052 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_12575.trc
***
Corrupt block relative dba: 0x0686e1ec (file 26, block 451052)
Bad check value found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x0686e1ec
last change scn: 0x0717.bc910322 seq: 0x1 flg: 0x06
consistency value in tail: 0x03220601
check value in block header: 0x2c90, computed block checksum: 0xb43
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of rdba: 0x0686e1ec (file 26, block 451052) found same corrupted data
Wed Dec 26 01:32:32 2007
Thread 1 advanced to log sequence 84
Current log# 3 seq# 84 mem# 0: /opt/oracle/oradata/BIMS/redo03.log
Wed Dec 26 01:32:32 2007
ARC0: Evaluating archive log 2 thread 1 sequence 83
ARC0: Beginning to archive log 2 thread 1 sequence 83
Creating archive destination LOG_ARCHIVE_DEST_1: '/archive/1_83.dbf'
ARC0: Completed archiving log 2 thread 1 sequence 83
Wed Dec 26 01:43:26 2007
Hex dump of Absolute File 22, Block 272269 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_13258.trc
***
Corrupt block relative dba: 0x0584278d (file 22, block 272269)
Fractured block found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x0584278d
last change scn: 0x0717.ad105707 seq: 0x1 flg: 0x06
consistency value in tail: 0x00304a49
check value in block header: 0x32fa, computed block checksum: 0xa750
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of rdba: 0x0584278d (file 22, block 272269) found same corrupted data
Wed Dec 26 01:44:02 2007
Hex dump of Absolute File 1, Block 46206 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_13033.trc
***
Corrupt block relative dba: 0x0040b47e (file 1, block 46206)
Bad check value found during backing up datafile
Data in bad block -
type: 6 format: 2 rdba: 0x0040b47e
last change scn: 0x0717.374a0a6b seq: 0x1 flg: 0x06
consistency value in tail: 0x0a6b0601
check value in block header: 0xcf7b, computed block checksum: 0x9c82
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of blocknum=46206, file=/opt/oracle/oradata/BIMS/system01.dbf. found same corrupt data
Wed Dec 26 02:07:14 2007
Hex dump of Absolute File 11, Block 445 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_14258.trc
***
Corrupt block relative dba: 0x02c001bd (file 11, block 445)
Bad check value found during backing up datafile
Data in bad block -
type: 0 format: 2 rdba: 0x02c001bd
last change scn: 0x0000.00000000 seq: 0x1 flg: 0x05
consistency value in tail: 0x00000001
check value in block header: 0x27b, computed block checksum: 0xcc4a
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of blocknum=445, file=/bimsdata/bims/idr.dbf. found same corrupt data
Wed Dec 26 02:14:34 2007
Hex dump of Absolute File 26, Block 284698 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_13069.trc
***
Corrupt block relative dba: 0x0684581a (file 26, block 284698)
Bad check value found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x0684581a
last change scn: 0x0717.b5dc9ca8 seq: 0x1 flg: 0x06
consistency value in tail: 0x9ca80601
check value in block header: 0xd4ec, computed block checksum: 0x8d9e
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of rdba: 0x0684581a (file 26, block 284698) found same corrupted data
Wed Dec 26 02:15:23 2007
Thread 1 advanced to log sequence 85
Current log# 1 seq# 85 mem# 0: /opt/oracle/oradata/BIMS/redo01.log
Wed Dec 26 02:15:23 2007
ARC1: Evaluating archive log 3 thread 1 sequence 84
ARC1: Beginning to archive log 3 thread 1 sequence 84
Creating archive destination LOG_ARCHIVE_DEST_1: '/archive/1_84.dbf'
ARC1: Completed archiving log 3 thread 1 sequence 84
Wed Dec 26 03:16:47 2007
Hex dump of Absolute File 17, Block 44939 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_17288.trc
***
Corrupt block relative dba: 0x0440af8b (file 17, block 44939)
Bad check value found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x0440af8b
last change scn: 0x0000.00d8d25b seq: 0x1 flg: 0x06
consistency value in tail: 0xd25b0601
check value in block header: 0x1ac, computed block checksum: 0x5f65
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of rdba: 0x0440af8b (file 17, block 44939) found same corrupted data
Wed Dec 26 03:31:42 2007
Thread 1 advanced to log sequence 86
Current log# 2 seq# 86 mem# 0: /opt/oracle/oradata/BIMS/redo02.log
Wed Dec 26 03:31:42 2007
ARC1: Evaluating archive log 1 thread 1 sequence 85
ARC1: Beginning to archive log 1 thread 1 sequence 85
Creating archive destination LOG_ARCHIVE_DEST_1: '/archive/1_85.dbf'
ARC1: Completed archiving log 1 thread 1 sequence 85
Wed Dec 26 05:01:52 2007
Thread 1 advanced to log sequence 87
Current log# 3 seq# 87 mem# 0: /opt/oracle/oradata/BIMS/redo03.log
Wed Dec 26 05:01:52 2007
ARC1: Evaluating archive log 2 thread 1 sequence 86
ARC1: Beginning to archive log 2 thread 1 sequence 86
Creating archive destination LOG_ARCHIVE_DEST_1: '/archive/1_86.dbf'
ARC1: Completed archiving log 2 thread 1 sequence 86
Wed Dec 26 05:05:57 2007
Hex dump of Absolute File 1, Block 46206 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_21644.trc
***
Corrupt block relative dba: 0x0040b47e (file 1, block 46206)
Bad check value found during backing up datafile
Data in bad block -
type: 6 format: 2 rdba: 0x0040b47e
last change scn: 0x0717.374a0a6b seq: 0x1 flg: 0x06
consistency value in tail: 0x0a6b0601
check value in block header: 0xcf7b, computed block checksum: 0x9c82
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of blocknum=46206, file=/opt/oracle/oradata/BIMS/system01.dbf. found same corrupt data
Hex dump of Absolute File 1, Block 46207 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_21644.trc
***
Corrupt block relative dba: 0x0040b47f (file 1, block 46207)
Bad check value found during backing up datafile
Data in bad block -
type: 6 format: 2 rdba: 0x0040b47f
last change scn: 0x0717.374a0a6b seq: 0x1 flg: 0x06
consistency value in tail: 0x0a6b0601
check value in block header: 0xe815, computed block checksum: 0xa360
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of blocknum=46207, file=/opt/oracle/oradata/BIMS/system01.dbf. found same corrupt data
Hex dump of Absolute File 26, Block 85849 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_21644.trc
***
Corrupt block relative dba: 0x06814f59 (file 26, block 85849)
Bad check value found during backing up datafile
Data in bad block -
type: 6 format: 2 rdba: 0x06814f59
last change scn: 0x0717.4fb5b97c seq: 0x1 flg: 0x04
consistency value in tail: 0xb97c0601
check value in block header: 0xbf25, computed block checksum: 0x9a12
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of blocknum=85849, file=/bimsdata/bims/bill8.dbf. found same corrupt data
Hex dump of Absolute File 26, Block 85850 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_21644.trc
***
Corrupt block relative dba: 0x06814f5a (file 26, block 85850)
Bad check value found during backing up datafile
Data in bad block -
type: 6 format: 2 rdba: 0x06814f5a
last change scn: 0x0717.4fb5bfcb seq: 0x2 flg: 0x04
consistency value in tail: 0xbfcb0602
check value in block header: 0x9d95, computed block checksum: 0x7c07
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of blocknum=85850, file=/bimsdata/bims/bill8.dbf. found same corrupt data
Hex dump of Absolute File 21, Block 96051 in trace file /opt/oracle/admin/BIMS/udump/bims_ora_21644.trc
***
Corrupt block relative dba: 0x05417733 (file 21, block 96051)
Bad check value found during backing up datafile
Data in bad block -
type: 6 format: 2 rdba: 0x05417733
last change scn: 0x0000.00a158e0 seq: 0x1 flg: 0x06
consistency value in tail: 0x58e00601
check value in block header: 0xb58, computed block checksum: 0xea76
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of blocknum=96051, file=/bimsdata/bims/bill3.dbf. found same corrupt data
为何突然出现如此多的坏块，如何解决呢？多谢各位了。
trc文件内容：
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
ORACLE_HOME = /opt/oracle/product/9.2.0
System name: SunOS
Node name: hbJF-1
Release: 5.9
Version: Generic_122300-02
Machine: sun4u
Instance name: BIMS
Redo thread mounted by this instance: 1
Oracle process number: 21
Unix process pid: 12575, image: oracle@hbJF-1 (TNS V1-V3)
*** 2007-12-26 01:32:01.074
*** SESSION ID11.46) 2007-12-26 01:32:01.073
Hex dump of Absolute File 26, Block 451052
Dump of memory from 0x00000003E67B0000 to 0x00000003E67B2000
3E67B0000 06020000 0686E1EC BC910322 07170106 [..........."....]
.................
3E67B1FD0 50505030 30303030 33623166 3565300C
3E67B1FE0 42443930 31303436 38374132 02C1030A
3E67B1FF0 62792074 72696767 65720180 03220601
***
Corrupt block relative dba: 0x0686e1ec (file 26, block 451052)
Bad check value found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x0686e1ec
last change scn: 0x0717.bc910322 seq: 0x1 flg: 0x06
consistency value in tail: 0x03220601
check value in block header: 0x2c90, computed block checksum: 0xb43
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of rdba: 0x0686e1ec (file 26, block 451052) found same corrupted data
$
没有备份，在这之前已经是通过recover database using backup controlfile until cancel恢复的，然后open resetlogs了。
然后运行了一段时间，被人重启过以后，就抱下面的错误了。什么原因引起的呢？
有几个索引出现坏块已经重建完成，但还有下面的表有坏块：
分区表DAILYSESSION_TABLE的分区DAILYSESSION_P18和DAILYSESSION_P22
普通表APPCURRSESSION_TABLE，LOG_TABLE
系统表：SOURCE$
这该如何处理？
为何设置了事件，对于分区表还是不行呢？
'10231 trace name context forever,level 10'
SQL> ALTER SYSTEM SET EVENTS='10231 trace name context forever,level 10';
系统已更改。
已用时间: 00: 00: 00.02
SQL> !
$ rm /archive/jyc/APPCURRSESSION_TABLE_P18.dmp
$ exp system/xxx file=/archive/jyc/APPCURRSESSION_TABLE_P18.dmp log=/archive/jyc/APPCURRSESSION_TABLE_P18.log tables=BILL.APPCURRSESSION_TABLEAILYSESSION_P18
Export: Release 9.2.0.8.0 - Production on 星期三 12月 26 10:04:42 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
连接到: Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
已导出 ZHS16GBK 字符集和 AL16UTF16 NCHAR 字符集
即将导出指定的表通过常规路径 ...
当前的用户已更改为 BILL
. . 正在导出表 APPCURRSESSION_TABLE 16 行被导出
EXP-00050: 无法在执行分区导出"DAILYSESSION_P18"，在未分区表"APPCURRSESSION_TABLE"
导出成功终止，但出现警告。
SQL> ALTER SYSTEM SET EVENTS='10231 trace name context off';
系统已更改。
已用时间: 00: 00: 00.00
分区表也可以导出，上面是写错表名了。
对于系统表：SOURCE$，有坏块如何恢复？
页:
[1]