ORA-00600: internal error code, arguments: [4194] 问题处理

2023-10-17 02:58

本文主要是介绍ORA-00600: internal error code, arguments: [4194] 问题处理,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!



ORA-00600: internal error code, arguments: [4194]


今天再次偶遇ora-600 4194/4193 这个问题,这里再记录一下,这次处理相较上一次处理过程简单多了,这次故障我觉得是服务器突然断电造成的。

操作过程:
SQL> startup
ORACLE instance started.

Total System Global Area  583008256 bytes
Fixed Size                  2022504 bytes
Variable Size             184550296 bytes
Database Buffers          394264576 bytes
Redo Buffers                2170880 bytes
Database mounted.
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4194], [22], [39], [], [], [], [],
[]


----查看alertlog,确定具体错误:

SQL> show parameter dump

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
background_core_dump                 string      partial
background_dump_dest                 string      /oracle/admin/lixora/bdump
core_dump_dest                       string      /oracle/admin/lixora/cdump
max_dump_file_size                   string      UNLIMITED
shadow_core_dump                     string      PARTIAL
user_dump_dest                       string      /oracle/admin/lixora/udump



alertlog 如下:
Mon Dec  2 11:55:57 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.473.16, scn 0.7418494
Mon Dec  2 11:55:58 2013
Errors in file /oracle/admin/lixora/bdump/lixora_m000_3764.trc:
ORA-00600: internal error code, arguments: [4193], [1442], [1446], [], [], [], [], []
Doing block recovery for file 2 block 114
Block recovery from logseq 36, block 70 to scn 7418420
Mon Dec  2 11:56:01 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.72.16, scn 0.7418421
Doing block recovery for file 2 block 121
Block recovery from logseq 36, block 70 to scn 7418496
Mon Dec  2 11:56:01 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.475.16, scn 0.7418497
Mon Dec  2 11:56:01 2013
Errors in file /oracle/admin/lixora/bdump/lixora_m000_3764.trc:
ORA-00600: internal error code, arguments: [4194], [22], [39], [], [], [], [], []
Doing block recovery for file 2 block 630
Block recovery from logseq 36, block 72 to scn 7418428
Mon Dec  2 11:56:05 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.76.16, scn 0.7418429
Doing block recovery for file 2 block 105
Block recovery from logseq 36, block 72 to scn 7418498
Mon Dec  2 11:56:05 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.477.16, scn 0.7418499
Mon Dec  2 11:56:05 2013
Errors in file /oracle/admin/lixora/bdump/lixora_m000_3764.trc:
ORA-00600: internal error code, arguments: [4193], [1620], [1623], [], [], [], [], []
Mon Dec  2 11:56:20 2013
Doing block recovery for file 2 block 1525
Block recovery from logseq 36, block 76 to scn 7418431
Mon Dec  2 11:56:20 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.78.16, scn 0.7418433
Doing block recovery for file 2 block 9
Block recovery from logseq 36, block 61 to scn 7418500
Mon Dec  2 11:56:20 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.479.16, scn 0.7418502
Mon Dec  2 11:58:23 2013
Errors in file /oracle/admin/lixora/bdump/lixora_mmon_3734.trc:
ORA-00600: internal error code, arguments: [4193], [3393], [3397], [], [], [], [], []
Mon Dec  2 11:58:25 2013
Doing block recovery for file 2 block 194
Block recovery from logseq 36, block 59 to scn 7418411
Mon Dec  2 11:58:25 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.68.16, scn 0.7418413
Doing block recovery for file 2 block 153
Block recovery from logseq 36, block 59 to scn 7418553
Mon Dec  2 11:58:25 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.544.16, scn 0.7418554
ORA-607 encountered when generating server alert SMG-3503
Mon Dec  2 11:59:25 2013
Errors in file /oracle/admin/lixora/bdump/lixora_mmon_3734.trc:
ORA-00600: internal error code, arguments: [4194], [21], [28], [], [], [], [], []
Mon Dec  2 11:59:28 2013
Doing block recovery for file 2 block 172
Block recovery from logseq 36, block 64 to scn 7418410
Mon Dec  2 11:59:28 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.68.16, scn 0.7418413
Doing block recovery for file 2 block 89
Block recovery from logseq 36, block 64 to scn 7418576
Mon Dec  2 11:59:28 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.565.16, scn 0.7418577
ORA-607 encountered when generating server alert SMG-3503
Mon Dec  2 12:00:22 2013
Errors in file /oracle/admin/lixora/bdump/lixora_mmon_3734.trc:
ORA-00600: internal error code, arguments: [4193], [1442], [1446], [], [], [], [], []
Mon Dec  2 12:00:25 2013
Doing block recovery for file 2 block 114
Block recovery from logseq 36, block 70 to scn 7418420
Mon Dec  2 12:00:25 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.72.16, scn 0.7418421
Doing block recovery for file 2 block 121
Block recovery from logseq 36, block 70 to scn 7418595
Mon Dec  2 12:00:25 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.576.16, scn 0.7418596
Mon Dec  2 12:00:27 2013
Errors in file /oracle/admin/lixora/bdump/lixora_smon_3728.trc:
ORA-00600: internal error code, arguments: [4194], [22], [39], [], [], [], [], []
Mon Dec  2 12:00:28 2013
Errors in file /oracle/admin/lixora/bdump/lixora_mmon_3734.trc:
ORA-00600: internal error code, arguments: [4193], [1620], [1623], [], [], [], [], []
Mon Dec  2 12:00:29 2013
Doing block recovery for file 2 block 630
Block recovery from logseq 36, block 72 to scn 7418428
Mon Dec  2 12:00:29 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.76.16, scn 0.7418429
Doing block recovery for file 2 block 105
Block recovery from logseq 36, block 72 to scn 7418597
Mon Dec  2 12:00:29 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 36 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/lixora/redo03.log
Block recovery completed at rba 36.581.16, scn 0.7418598
Mon Dec  2 12:00:29 2013
Errors in file /oracle/admin/lixora/bdump/lixora_smon_3728.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4194], [22], [39], [], [], [], [], []


----发现数据文件id:2的文件有问题,默认情况下,id为2的数据文件为undo 数据文件。在mount状态下确认id为2的数据库文件是什么?
[oracle@localhost ~]$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.1.0 - Production on Mon Dec 2 12:01:22 2013

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


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options

SQL> select * from dba_data_files where file_id=2;

FILE_NAME
--------------------------------------------------------------------------------
   FILE_ID TABLESPACE_NAME                     BYTES     BLOCKS STATUS
---------- ------------------------------ ---------- ---------- ---------
RELATIVE_FNO AUT   MAXBYTES  MAXBLOCKS INCREMENT_BY USER_BYTES USER_BLOCKS
------------ --- ---------- ---------- ------------ ---------- -----------
ONLINE_
-------
/oracle/oradata/lixora/undotbs01.dbf
         2 UNDOTBS1                       1038090240     126720 AVAILABLE
           2 YES 3.4360E+10    4194302          640 1038024704      126712
ONLINE



----------开始修复数据库:------------
SQL>
SQL>
----设置undo表空间的管理方式为:手工,缺省undotbs 为空,实际上市使用了 system 回滚段。
SQL>  alter system set undo_management = manual scope=spfile;

System altered.

SQL>  alter system set undo_tablespace='' scope=spfile;

System altered.



SQL> startup force
ORACLE instance started.

Total System Global Area  583008256 bytes
Fixed Size                  2022504 bytes
Variable Size             184550296 bytes
Database Buffers          394264576 bytes
Redo Buffers                2170880 bytes
Database mounted.
Database opened.
SQL>
SQL>
----创建新的undo表空间:
SQL>  create undo tablespace undotbs2 
  2  datafile '/oracle/oradata/lixora/undotbs2.dbf' size 100M;

Tablespace created.

----设置undo管理方式为 ’自动‘:
SQL> alter system set undo_management =auto scope=spfile;

System altered.


----设置undotbs 为新建的undotbs2:
SQL> alter system set undo_tablespace = undotbs2 scope=spfile;

System altered.


----删除原来损坏的undo表空间 :

SQL>  drop tablespace undotbs02 including contents and datafiles;

Tablespace dropped.

SQL> startup force;
ORACLE instance started.

Total System Global Area  583008256 bytes
Fixed Size                  2022504 bytes
Variable Size             234881944 bytes
Database Buffers          343932928 bytes
Redo Buffers                2170880 bytes
Database mounted.
Database opened.
SQL>
SQL>
SQL> 

这篇关于ORA-00600: internal error code, arguments: [4194] 问题处理的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!


原文地址:
本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.chinasem.cn/article/222472

相关文章

Python使用vllm处理多模态数据的预处理技巧

《Python使用vllm处理多模态数据的预处理技巧》本文深入探讨了在Python环境下使用vLLM处理多模态数据的预处理技巧,我们将从基础概念出发,详细讲解文本、图像、音频等多模态数据的预处理方法,... 目录1. 背景介绍1.1 目的和范围1.2 预期读者1.3 文档结构概述1.4 术语表1.4.1 核

Spring Boot @RestControllerAdvice全局异常处理最佳实践

《SpringBoot@RestControllerAdvice全局异常处理最佳实践》本文详解SpringBoot中通过@RestControllerAdvice实现全局异常处理,强调代码复用、统... 目录前言一、为什么要使用全局异常处理?二、核心注解解析1. @RestControllerAdvice2

怎样通过分析GC日志来定位Java进程的内存问题

《怎样通过分析GC日志来定位Java进程的内存问题》:本文主要介绍怎样通过分析GC日志来定位Java进程的内存问题,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录一、GC 日志基础配置1. 启用详细 GC 日志2. 不同收集器的日志格式二、关键指标与分析维度1.

Java 线程安全与 volatile与单例模式问题及解决方案

《Java线程安全与volatile与单例模式问题及解决方案》文章主要讲解线程安全问题的五个成因(调度随机、变量修改、非原子操作、内存可见性、指令重排序)及解决方案,强调使用volatile关键字... 目录什么是线程安全线程安全问题的产生与解决方案线程的调度是随机的多个线程对同一个变量进行修改线程的修改操

Redis出现中文乱码的问题及解决

《Redis出现中文乱码的问题及解决》:本文主要介绍Redis出现中文乱码的问题及解决,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录1. 问题的产生2China编程. 问题的解决redihttp://www.chinasem.cns数据进制问题的解决中文乱码问题解决总结

全面解析MySQL索引长度限制问题与解决方案

《全面解析MySQL索引长度限制问题与解决方案》MySQL对索引长度设限是为了保持高效的数据检索性能,这个限制不是MySQL的缺陷,而是数据库设计中的权衡结果,下面我们就来看看如何解决这一问题吧... 目录引言:为什么会有索引键长度问题?一、问题根源深度解析mysql索引长度限制原理实际场景示例二、五大解决

Springboot如何正确使用AOP问题

《Springboot如何正确使用AOP问题》:本文主要介绍Springboot如何正确使用AOP问题,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录​一、AOP概念二、切点表达式​execution表达式案例三、AOP通知四、springboot中使用AOP导出

Python中Tensorflow无法调用GPU问题的解决方法

《Python中Tensorflow无法调用GPU问题的解决方法》文章详解如何解决TensorFlow在Windows无法识别GPU的问题,需降级至2.10版本,安装匹配CUDA11.2和cuDNN... 当用以下代码查看GPU数量时,gpuspython返回的是一个空列表,说明tensorflow没有找到

解决未解析的依赖项:‘net.sf.json-lib:json-lib:jar:2.4‘问题

《解决未解析的依赖项:‘net.sf.json-lib:json-lib:jar:2.4‘问题》:本文主要介绍解决未解析的依赖项:‘net.sf.json-lib:json-lib:jar:2.4... 目录未解析的依赖项:‘net.sf.json-lib:json-lib:jar:2.4‘打开pom.XM

IDEA Maven提示:未解析的依赖项的问题及解决

《IDEAMaven提示:未解析的依赖项的问题及解决》:本文主要介绍IDEAMaven提示:未解析的依赖项的问题及解决,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝... 目录IDEA Maven提示:未解析的依编程赖项例如总结IDEA Maven提示:未解析的依赖项例如