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

相关文章

SpringBoot操作spark处理hdfs文件的操作方法

《SpringBoot操作spark处理hdfs文件的操作方法》本文介绍了如何使用SpringBoot操作Spark处理HDFS文件,包括导入依赖、配置Spark信息、编写Controller和Ser... 目录SpringBoot操作spark处理hdfs文件1、导入依赖2、配置spark信息3、cont

解决mybatis-plus-boot-starter与mybatis-spring-boot-starter的错误问题

《解决mybatis-plus-boot-starter与mybatis-spring-boot-starter的错误问题》本文主要讲述了在使用MyBatis和MyBatis-Plus时遇到的绑定异常... 目录myBATis-plus-boot-starpythonter与mybatis-spring-b

mysql主从及遇到的问题解决

《mysql主从及遇到的问题解决》本文详细介绍了如何使用Docker配置MySQL主从复制,首先创建了两个文件夹并分别配置了`my.cnf`文件,通过执行脚本启动容器并配置好主从关系,文中还提到了一些... 目录mysql主从及遇到问题解决遇到的问题说明总结mysql主从及遇到问题解决1.基于mysql

如何测试计算机的内存是否存在问题? 判断电脑内存故障的多种方法

《如何测试计算机的内存是否存在问题?判断电脑内存故障的多种方法》内存是电脑中非常重要的组件之一,如果内存出现故障,可能会导致电脑出现各种问题,如蓝屏、死机、程序崩溃等,如何判断内存是否出现故障呢?下... 如果你的电脑是崩溃、冻结还是不稳定,那么它的内存可能有问题。要进行检查,你可以使用Windows 11

如何安装HWE内核? Ubuntu安装hwe内核解决硬件太新的问题

《如何安装HWE内核?Ubuntu安装hwe内核解决硬件太新的问题》今天的主角就是hwe内核(hardwareenablementkernel),一般安装的Ubuntu都是初始内核,不能很好地支... 对于追求系统稳定性,又想充分利用最新硬件特性的 Ubuntu 用户来说,HWEXBQgUbdlna(Har

MAVEN3.9.x中301问题及解决方法

《MAVEN3.9.x中301问题及解决方法》本文主要介绍了使用MAVEN3.9.x中301问题及解决方法,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友们下面... 目录01、背景02、现象03、分析原因04、解决方案及验证05、结语本文主要是针对“构建加速”需求交

MyBatis延迟加载的处理方案

《MyBatis延迟加载的处理方案》MyBatis支持延迟加载(LazyLoading),允许在需要数据时才从数据库加载,而不是在查询结果第一次返回时就立即加载所有数据,延迟加载的核心思想是,将关联对... 目录MyBATis如何处理延迟加载?延迟加载的原理1. 开启延迟加载2. 延迟加载的配置2.1 使用

Android WebView的加载超时处理方案

《AndroidWebView的加载超时处理方案》在Android开发中,WebView是一个常用的组件,用于在应用中嵌入网页,然而,当网络状况不佳或页面加载过慢时,用户可能会遇到加载超时的问题,本... 目录引言一、WebView加载超时的原因二、加载超时处理方案1. 使用Handler和Timer进行超

Python中处理NaN值的技巧分享

《Python中处理NaN值的技巧分享》在数据科学和数据分析领域,NaN(NotaNumber)是一个常见的概念,它表示一个缺失或未定义的数值,在Python中,尤其是在使用pandas库处理数据时,... 目录NaN 值的来源和影响使用 pandas 的 isna()和 isnull()函数直接比较 Na

Nginx、Tomcat等项目部署问题以及解决流程

《Nginx、Tomcat等项目部署问题以及解决流程》本文总结了项目部署中常见的four类问题及其解决方法:Nginx未按预期显示结果、端口未开启、日志分析的重要性以及开发环境与生产环境运行结果不一致... 目录前言1. Nginx部署后未按预期显示结果1.1 查看Nginx的启动情况1.2 解决启动失败的