li
  当前位置:主页 > 性能优化 > 文章内容
li
ORA-00600: internal error code, arguments [4194]错误
来源: www.ixdba.net  作者: IXDBA.NET官方    时间:2008-03-13   阅读:24  
本文章共3381字,分3页,当前第1页,快速翻页:
 
问题描述:我的数据库重新启动后,出现了Ora-00600 4194错误,具体的日志如下:

Sat Jan 21 13:55:21 2006
Errors in file /opt/oracle/admin/conner
/bdump/conner_smon_17113.trc:
ORA-00600: internal error code, arguments: 
[4194], [43], [46], [], [], [], [], []
Sat Jan 21 13:55:21 2006
Errors in file /opt/oracle/admin/conner
/udump/conner_ora_17121.trc:
ORA-00600: internal error code, arguments: 
[4194], [45], [44], [], [], [], [], []
请问应该用什么办法解决?

  答:具体的解决办法是通过备份来进行恢复,因为Ora-00600 4194错误的出现说明UNDO段出现了问题,如果你没有备份,业可以通过特殊的初始化参数进行强制启动,下文针对Oracle的隐含参数进行恢复说明(由于你的实际情况可能会有所出入,所以请你进行测试前先行备份)。

  ◆首先你需要确定当前的回滚段名称,注释:(可以从alert文件中获得)

Sat Jan 21 13:55:21 2006
Undo Segment 11 Onlined
Undo Segment 12 Onlined
Undo Segment 13 Onlined
Successfully onlined Undo Tablespace 16

  ◆注意:对应的AUM (auto undo management) 下的回滚段名称为:

  '_SYSSMU11$','_SYSSMU12$','_SYSSMU13$'

  ◆此时你可以修改init.ora参数文件,使用Oracle隐含参数_corrupted_rollback_segments将回滚段标记为损坏,然后启动数据库,Oracle则会跳过对于这些回滚段的相关操作,强制启动数据库。

  。_corrupted_rollback_segments='_SYSSMU11$','_SYSSMU12$','_SYSSMU13$'

  ◆然后使用init.ora参数文件启动数据库:

[oracle@jumper dbs]$ sqlplus "/ as sysdba"
SQL*Plus: Release 9.2.0.4.0 - Production on Sat Jan 21 13:56:47 2006
Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
Connected to an idle instance.
SQL> startup pfile=initconner.ora
ORACLE instance started.
Total System Global Area   97588504 bytes
Fixed Size                   451864 bytes
Variable Size              33554432 bytes
Database Buffers           62914560 bytes
Redo Buffers                 667648 bytes
Database mounted.
Database opened.

  至此数据库正常Open.

  ◆注意观察alert文件所获得的如下信息:

Sat Jan 21 13:57:03 2006
SMON: enabling tx recovery
SMON: about to recover undo segment 11
SMON: mark undo segment 11 as needs recovery
SMON: about to recover undo segment 12
SMON: mark undo segment 12 as needs recovery
SMON: about to recover undo segment 13
SMON: mark undo segment 13 as needs recovery
Sat Jan 21 13:57:03 2006
Database Characterset is ZHS16GBK
Sat Jan 21 13:57:03 2006
SMON: about to recover undo segment 11
SMON: mark undo segment 11 as needs recovery
SMON: about to recover undo segment 12
SMON: mark undo segment 12 as needs recovery
SMON: about to recover undo segment 13
SMON: mark undo segment 13 as needs recovery
Sat Jan 21 13:57:04 2006
Created Undo Segment _SYSSMU1$
Undo Segment 1 Onlined
Completed: ALTER DATABASE OPEN
aSat Jan 21 14:02:11 2006
SMON: about to recover undo segment 11
SMON: mark undo segment 11 as needs recovery
SMON: about to recover undo segment 12
SMON: mark undo segment 12 as needs recovery
SMON: about to recover undo segment 13
SMON: mark undo segment 13 as needs recovery



阅读更多内容1 · 2 · 3 · 下一页>>


  上一篇: Oracle中ORA-01599错误的解决方法   下一篇: 如何解决ora-600 12700错误
li
 §相关评论  
 热点文章

·Resize datafile导致ASM Crash
·在Oracle10g RAC下新增ASM磁盘
·ORACLE SQL性能优化系列 (一)
·oracle性能调优:管理oracle日志
·oracle RAC环境中系统时钟的调
·why:Rac的心跳线不支持交叉线?
·RAC的VIP及实例依赖关系:版本O
·如何启动DataGuard的备用数据库
·系统表空间IO错误 数据损坏处理
·不幸中的万幸:遭遇ORA-00600 [
·用ORACLE的高级复制实现内外网
li
 编辑推荐
·Resize datafile导致ASM Crash
·在Oracle10g RAC下新增ASM磁盘
·ORACLE SQL性能优化系列 (一)
·oracle性能调优:管理oracle日志
·oracle RAC环境中系统时钟的调
·why:Rac的心跳线不支持交叉线?
·RAC的VIP及实例依赖关系:版本O
·如何启动DataGuard的备用数据库
·系统表空间IO错误 数据损坏处理
·不幸中的万幸:遭遇ORA-00600 [
·用ORACLE的高级复制实现内外网
li
 相关篇章
·Oracle中ORA-01599错误的解决方法
·ORA-12154: TNS: 无法解析指定的...
·ORA-01562 和 ORA-01628 问题解决...
·ora-02069 错误解决方法
·ORA-00600: 内部错误代码,参数:...
·streams流复制ORA-01403错误解决...
·Oracle10gR2 ORA-3136 错误解决方...
·Oracle中ORA-01599错误的解决方法
·Oracle10gR2 Dataguard 环境ORA-...
·Oracle 11g最有特点的五大新特性
·如何解决ora-600 12700错误
·ora-12638:身份证明检索失败的解...
·ORA-04098错误解决方法
·ORA-600 [2103]错误解决过程
·ORA-00701 warmstarting对象的另...
·ORACLE ORA-1693错误以及表和索...
·oracle ora-01861文字与格式字符...
·ORA-00904 invalid column name案...
·oracle ORA-01991错误--重建密码...
·oracle中ora-0100错误打开游标过...
 
li
设为首页 | 关于我们 | 技术服务 | 收藏本站 | 网站地图 | 联系方式 | 本站友情连接