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

相关文章

IDEA和GIT关于文件中LF和CRLF问题及解决

《IDEA和GIT关于文件中LF和CRLF问题及解决》文章总结:因IDEA默认使用CRLF换行符导致Shell脚本在Linux运行报错,需在编辑器和Git中统一为LF,通过调整Git的core.aut... 目录问题描述问题思考解决过程总结问题描述项目软件安装shell脚本上git仓库管理,但拉取后,上l

解决docker目录内存不足扩容处理方案

《解决docker目录内存不足扩容处理方案》文章介绍了Docker存储目录迁移方法:因系统盘空间不足,需将Docker数据迁移到更大磁盘(如/home/docker),通过修改daemon.json配... 目录1、查看服务器所有磁盘的使用情况2、查看docker镜像和容器存储目录的空间大小3、停止dock

idea npm install很慢问题及解决(nodejs)

《ideanpminstall很慢问题及解决(nodejs)》npm安装速度慢可通过配置国内镜像源(如淘宝)、清理缓存及切换工具解决,建议设置全局镜像(npmconfigsetregistryht... 目录idea npm install很慢(nodejs)配置国内镜像源清理缓存总结idea npm in

pycharm跑python项目易出错的问题总结

《pycharm跑python项目易出错的问题总结》:本文主要介绍pycharm跑python项目易出错问题的相关资料,当你在PyCharm中运行Python程序时遇到报错,可以按照以下步骤进行排... 1. 一定不要在pycharm终端里面创建环境安装别人的项目子模块等,有可能出现的问题就是你不报错都安装

idea突然报错Malformed \uxxxx encoding问题及解决

《idea突然报错Malformeduxxxxencoding问题及解决》Maven项目在切换Git分支时报错,提示project元素为描述符根元素,解决方法:删除Maven仓库中的resolv... 目www.chinasem.cn录问题解决方式总结问题idea 上的 maven China编程项目突然报错,是

Python爬虫HTTPS使用requests,httpx,aiohttp实战中的证书异步等问题

《Python爬虫HTTPS使用requests,httpx,aiohttp实战中的证书异步等问题》在爬虫工程里,“HTTPS”是绕不开的话题,HTTPS为传输加密提供保护,同时也给爬虫带来证书校验、... 目录一、核心问题与优先级检查(先问三件事)二、基础示例:requests 与证书处理三、高并发选型:

5 种使用Python自动化处理PDF的实用方法介绍

《5种使用Python自动化处理PDF的实用方法介绍》自动化处理PDF文件已成为减少重复工作、提升工作效率的重要手段,本文将介绍五种实用方法,从内置工具到专业库,帮助你在Python中实现PDF任务... 目录使用内置库(os、subprocess)调用外部工具使用 PyPDF2 进行基本 PDF 操作使用

前端导出Excel文件出现乱码或文件损坏问题的解决办法

《前端导出Excel文件出现乱码或文件损坏问题的解决办法》在现代网页应用程序中,前端有时需要与后端进行数据交互,包括下载文件,:本文主要介绍前端导出Excel文件出现乱码或文件损坏问题的解决办法,... 目录1. 检查后端返回的数据格式2. 前端正确处理二进制数据方案 1:直接下载(推荐)方案 2:手动构造

分析 Java Stream 的 peek使用实践与副作用处理方案

《分析JavaStream的peek使用实践与副作用处理方案》StreamAPI的peek操作是中间操作,用于观察元素但不终止流,其副作用风险包括线程安全、顺序混乱及性能问题,合理使用场景有限... 目录一、peek 操作的本质:有状态的中间操作二、副作用的定义与风险场景1. 并行流下的线程安全问题2. 顺

Python绘制TSP、VRP问题求解结果图全过程

《Python绘制TSP、VRP问题求解结果图全过程》本文介绍用Python绘制TSP和VRP问题的静态与动态结果图,静态图展示路径,动态图通过matplotlib.animation模块实现动画效果... 目录一、静态图二、动态图总结【代码】python绘制TSP、VRP问题求解结果图(包含静态图与动态图