00600 ora 关闭oracle_Oracle断电报错ORA-00600数据库无法打开的恢复

以下为一个ORACLE数据库因为断掉而引起ORA-00600错误的例子。

造成ORA-00600 [4000]错误的主要原因是因为系统掉电,或者数据库恢复不完全,导致system表空间的一些位的状态异常,导致bootstrap无法正常情况.

以下是通过bbed方法,修改相关标志位,强制打开数据库的一种方法.

但是由于数据库实际上已经处于非一致状态,强烈建议用户打开数据库后,通过将生产环境的数据导出后,重建数据库.

--alert log相关的trace如下:

Tue Jun  4 15:41:34 2013

Errors in file /u02/oracle/app/oracle/admin/ORCL/udump/ORCL1_ora_770332.trc:

ORA-00600: internal error code, arguments: [4000], [41], [], [], [], [], [], []

trace文件 /u02/oracle/app/oracle/admin/ORCL/udump/ORCL1_ora_770332.trc,可以找到类似的相关内容

*** 2013-06-04 15:41:35.055

ksedmp: internal or fatal error

ORA-00600: internal error code, arguments: [4000], [41], [], [], [], [], [], []

Current SQL statement for this session:

select ctime, mtime, stime from obj$ where obj# = :1

----- Call Stack Trace -----

calling              call     entry                argument values in hex

location             type     point                (? means dubious value)

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

ksedst+001c          bl       ksedst1              0FFFFFFFF ? 000000020 ?

ksedmp+0290          bl       ksedst               1048EBB20 ?

ksfdmp+0018          bl       03F3BE0C

kgeriv+0108          bl       _ptrgl

kgeasi+0118          bl       kgeriv               1019AAD00 ? 000000000 ?

000000000 ?

26414080048E1630 ?

300000000 ?

...................................................

Block header dump:  0x0040007a

Object id on Block? Y

seg/obj: 0x12  csc: 0xc20.26114c0d  itc: 1  flg: -  typ: 1 - DATA

fsl: 0  fnx: 0x0 ver: 0x01

Itl           Xid                  Uba         Flag  Lck        Scn/Fsc

0x01   0x0029.026.0021d127  0x0091a949.3d91.01  --U-    1  fsc 0x0000.26114c0f

data_block_dump,data header at 0x700000b77a4e044

===============

tsiz: 0x1fb8

hsiz: 0xea

pbl: 0x700000b77a4e044

bdba: 0x0040007a

76543210

flag=--------

ntab=1

nrow=108

frre=-1

fsbo=0xea

fseo=0x40c

avsp=0x368

tosp=0x368

这次一开始这个库报ORA-600[2662]错误:

Mon Aug 23 09:37:00 2010

Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_852096.trc:

ORA-00600: internal error code, arguments: [2662], [0], [130131504], [0], [130254136], [4264285], [], []

Mon Aug 23 09:37:02 2010

Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_852096.trc:

ORA-00600: internal error code, arguments: [2662], [0], [130131506], [0], [130254136], [4264285], [], []

Mon Aug 23 09:37:00 2010

Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_852096.trc:

ORA-00600: internal error code, arguments: [2662], [0], [130131504], [0], [130254136], [4264285], [], []

Mon Aug 23 09:37:02 2010

Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_852096.trc:

ORA-00600: internal error code, arguments: [2662], [0], [130131506], [0], [130254136], [4264285], [], []

以下为一些可能遇到的报错列表：

Error DescriptionCorruption related to:

ORA-1578ORA-1578一般为Oracle检测到存在物理坏块问题，包括其检测数据块中的checksum不正确，或者tail_chk信息不正确等。ORA-1578 is reported when a block is thought to be corrupt on read.

Block

数据块

OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)” Master Note

OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)”

Fractured Block explanation

Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g

Diagnosing and Resolving 1578 reported on a Local Index of a Partitioned table

ORA-1410

ORA-1410错误常见于从INDEX或其他途径获得的ROWID,到数据表中查询发现没有对应的记录。

该错误可能因为数据表与其索引存在不一致，也可能是