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

相关文章

无人叉车3d激光slam多房间建图定位异常处理方案-墙体画线地图切分方案

墙体画线地图切分方案 针对问题:墙体两侧特征混淆误匹配,导致建图和定位偏差,表现为过门跳变、外月台走歪等 ·解决思路:预期的根治方案IGICP需要较长时间完成上线,先使用切分地图的工程化方案,即墙体两侧切分为不同地图,在某一侧只使用该侧地图进行定位 方案思路 切分原理:切分地图基于关键帧位置,而非点云。 理论基础:光照是直线的,一帧点云必定只能照射到墙的一侧,无法同时照到两侧实践考虑:关

好题——hdu2522(小数问题:求1/n的第一个循环节)

好喜欢这题,第一次做小数问题,一开始真心没思路,然后参考了网上的一些资料。 知识点***********************************无限不循环小数即无理数,不能写作两整数之比*****************************(一开始没想到,小学没学好) 此题1/n肯定是一个有限循环小数,了解这些后就能做此题了。 按照除法的机制,用一个函数表示出来就可以了,代码如下

hdu1043(八数码问题,广搜 + hash(实现状态压缩) )

利用康拓展开将一个排列映射成一个自然数,然后就变成了普通的广搜题。 #include<iostream>#include<algorithm>#include<string>#include<stack>#include<queue>#include<map>#include<stdio.h>#include<stdlib.h>#include<ctype.h>#inclu

购买磨轮平衡机时应该注意什么问题和技巧

在购买磨轮平衡机时,您应该注意以下几个关键点: 平衡精度 平衡精度是衡量平衡机性能的核心指标,直接影响到不平衡量的检测与校准的准确性,从而决定磨轮的振动和噪声水平。高精度的平衡机能显著减少振动和噪声,提高磨削加工的精度。 转速范围 宽广的转速范围意味着平衡机能够处理更多种类的磨轮,适应不同的工作条件和规格要求。 振动监测能力 振动监测能力是评估平衡机性能的重要因素。通过传感器实时监

缓存雪崩问题

缓存雪崩是缓存中大量key失效后当高并发到来时导致大量请求到数据库,瞬间耗尽数据库资源,导致数据库无法使用。 解决方案: 1、使用锁进行控制 2、对同一类型信息的key设置不同的过期时间 3、缓存预热 1. 什么是缓存雪崩 缓存雪崩是指在短时间内,大量缓存数据同时失效,导致所有请求直接涌向数据库,瞬间增加数据库的负载压力,可能导致数据库性能下降甚至崩溃。这种情况往往发生在缓存中大量 k

【生成模型系列(初级)】嵌入(Embedding)方程——自然语言处理的数学灵魂【通俗理解】

【通俗理解】嵌入(Embedding)方程——自然语言处理的数学灵魂 关键词提炼 #嵌入方程 #自然语言处理 #词向量 #机器学习 #神经网络 #向量空间模型 #Siri #Google翻译 #AlexNet 第一节:嵌入方程的类比与核心概念【尽可能通俗】 嵌入方程可以被看作是自然语言处理中的“翻译机”,它将文本中的单词或短语转换成计算机能够理解的数学形式,即向量。 正如翻译机将一种语言

6.1.数据结构-c/c++堆详解下篇(堆排序,TopK问题)

上篇:6.1.数据结构-c/c++模拟实现堆上篇(向下,上调整算法,建堆,增删数据)-CSDN博客 本章重点 1.使用堆来完成堆排序 2.使用堆解决TopK问题 目录 一.堆排序 1.1 思路 1.2 代码 1.3 简单测试 二.TopK问题 2.1 思路(求最小): 2.2 C语言代码(手写堆) 2.3 C++代码(使用优先级队列 priority_queue)

【VUE】跨域问题的概念,以及解决方法。

目录 1.跨域概念 2.解决方法 2.1 配置网络请求代理 2.2 使用@CrossOrigin 注解 2.3 通过配置文件实现跨域 2.4 添加 CorsWebFilter 来解决跨域问题 1.跨域概念 跨域问题是由于浏览器实施了同源策略,该策略要求请求的域名、协议和端口必须与提供资源的服务相同。如果不相同,则需要服务器显式地允许这种跨域请求。一般在springbo

题目1254:N皇后问题

题目1254:N皇后问题 时间限制:1 秒 内存限制:128 兆 特殊判题:否 题目描述: N皇后问题,即在N*N的方格棋盘内放置了N个皇后,使得它们不相互攻击(即任意2个皇后不允许处在同一排,同一列,也不允许处在同一斜线上。因为皇后可以直走,横走和斜走如下图)。 你的任务是,对于给定的N,求出有多少种合法的放置方法。输出N皇后问题所有不同的摆放情况个数。 输入

vscode中文乱码问题,注释,终端,调试乱码一劳永逸版

忘记咋回事突然出现了乱码问题,很多方法都试了,注释乱码解决了,终端又乱码,调试窗口也乱码,最后经过本人不懈努力,终于全部解决了,现在分享给大家我的方法。 乱码的原因是各个地方用的编码格式不统一,所以把他们设成统一的utf8. 1.电脑的编码格式 开始-设置-时间和语言-语言和区域 管理语言设置-更改系统区域设置-勾选Bata版:使用utf8-确定-然后按指示重启 2.vscode