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

相关文章

mybatis和mybatis-plus设置值为null不起作用问题及解决

《mybatis和mybatis-plus设置值为null不起作用问题及解决》Mybatis-Plus的FieldStrategy主要用于控制新增、更新和查询时对空值的处理策略,通过配置不同的策略类型... 目录MyBATis-plusFieldStrategy作用FieldStrategy类型每种策略的作

linux下多个硬盘划分到同一挂载点问题

《linux下多个硬盘划分到同一挂载点问题》在Linux系统中,将多个硬盘划分到同一挂载点需要通过逻辑卷管理(LVM)来实现,首先,需要将物理存储设备(如硬盘分区)创建为物理卷,然后,将这些物理卷组成... 目录linux下多个硬盘划分到同一挂载点需要明确的几个概念硬盘插上默认的是非lvm总结Linux下多

Python Jupyter Notebook导包报错问题及解决

《PythonJupyterNotebook导包报错问题及解决》在conda环境中安装包后,JupyterNotebook导入时出现ImportError,可能是由于包版本不对应或版本太高,解决方... 目录问题解决方法重新安装Jupyter NoteBook 更改Kernel总结问题在conda上安装了

pip install jupyterlab失败的原因问题及探索

《pipinstalljupyterlab失败的原因问题及探索》在学习Yolo模型时,尝试安装JupyterLab但遇到错误,错误提示缺少Rust和Cargo编译环境,因为pywinpty包需要它... 目录背景问题解决方案总结背景最近在学习Yolo模型,然后其中要下载jupyter(有点LSVmu像一个

解决jupyterLab打开后出现Config option `template_path`not recognized by `ExporterCollapsibleHeadings`问题

《解决jupyterLab打开后出现Configoption`template_path`notrecognizedby`ExporterCollapsibleHeadings`问题》在Ju... 目录jupyterLab打开后出现“templandroidate_path”相关问题这是 tensorflo

如何解决Pycharm编辑内容时有光标的问题

《如何解决Pycharm编辑内容时有光标的问题》文章介绍了如何在PyCharm中配置VimEmulator插件,包括检查插件是否已安装、下载插件以及安装IdeaVim插件的步骤... 目录Pycharm编辑内容时有光标1.如果Vim Emulator前面有对勾2.www.chinasem.cn如果tools工

最长公共子序列问题的深度分析与Java实现方式

《最长公共子序列问题的深度分析与Java实现方式》本文详细介绍了最长公共子序列(LCS)问题,包括其概念、暴力解法、动态规划解法,并提供了Java代码实现,暴力解法虽然简单,但在大数据处理中效率较低,... 目录最长公共子序列问题概述问题理解与示例分析暴力解法思路与示例代码动态规划解法DP 表的构建与意义动

Java多线程父线程向子线程传值问题及解决

《Java多线程父线程向子线程传值问题及解决》文章总结了5种解决父子之间数据传递困扰的解决方案,包括ThreadLocal+TaskDecorator、UserUtils、CustomTaskDeco... 目录1 背景2 ThreadLocal+TaskDecorator3 RequestContextH

关于Spring @Bean 相同加载顺序不同结果不同的问题记录

《关于Spring@Bean相同加载顺序不同结果不同的问题记录》本文主要探讨了在Spring5.1.3.RELEASE版本下,当有两个全注解类定义相同类型的Bean时,由于加载顺序不同,最终生成的... 目录问题说明测试输出1测试输出2@Bean注解的BeanDefiChina编程nition加入时机总结问题说明

关于最长递增子序列问题概述

《关于最长递增子序列问题概述》本文详细介绍了最长递增子序列问题的定义及两种优化解法:贪心+二分查找和动态规划+状态压缩,贪心+二分查找时间复杂度为O(nlogn),通过维护一个有序的“尾巴”数组来高效... 一、最长递增子序列问题概述1. 问题定义给定一个整数序列,例如 nums = [10, 9, 2