[转帖]oracle 00600 4194 4193 问题的处理
oracle断电重启之ORA-00600[4194]
https://www.cnblogs.com/xwdreamer/p/3778383.html 部门的机器出现异常 断电导致的 错误 从网上学了下处理方法.
1.问题描述
Oracle服务器断电重启以后无法数据库无法正常连接,使用sqlplus envision/envision连接报错。常见的错误有以下这些:
- ORA-12518: TNS:listener could not hand off client connection
- ORA-12560: TNS:protocol adapter error
- ORA-01034: ORACLE not available
- ORA-27101: shared memory realm does not exist
- ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
- ORA-00600:[4194]
2.基本处理
上述这些ORA报错,基本可以归类为一下几种:
- 环境变量ORACLE_SID是否为prjdb,如果不是就设置环境变量
- TNSListener服务是否启动,如果没有启动就重新启动一下。
- prjdb这个oracle服务是否启动,如果没有启动就启动一下
- 使用dba身份能否连接oralce。
3.查看日志确认问题
将上面的这些问题都过一遍,并且都操作一遍以后发现问题还是没有解决,此时我们可以查看oracle 的alert log。我的alert log的路径为:
D:\app\oracle\diag\rdbms\prjdb\prjdb\trace\alert_prjdb.txt
打开alert log文件,找到日志的最后一行,发现行号是1003417,如下图所示:
接着尝试重启oracle服务,
重启完毕以后再次查看log文件,看看日志有什么错误。当我们找到ora-00600[4194]的时候,就定位到undo表空间文件损坏这个问题。最后解决方法就是重建undo表空间。
4.问题处理步骤:重建undo表空间
4.1思路:
在INITprjdb.ora这个配置文件中将undo表空间指向系统表空间system,然后删除undo表空间,最后在创建undo表空间,最后再在INITprjdb.ora这个配置文件中将undo表空间指向刚刚创建的undo表空间。
4.2查看表空间
select * from v$tablespace;
4.3查看undo表空间
show parameter undo
4.4管理员身份登陆:
sqlplus / as sysdba
4.5创建pfile
create pfile from spfile;
关闭实例
shutdown immediate
修改INITprjdb.ora参数
原始的值为:*.undo_tablespace='UNDOTBS1'
修改后的值为:
undo_management= MANUAL undo_tablespace= SYSTEM
这个可以参考:http://www.xifenfei.com/2111.html
启动数据库
在修改INITprjdb.ora以后,以INITprjdb.ora这个参数文件中的配置启动oracle实例
$SQL> startup pfile=D:\app\oracle\product\11.2.0\dbhome_1\database\INITprjdb.ora ORACLE instance started. Total System Global Area 857903104 bytes Fixed Size 1377952 bytes Variable Size 503318880 bytes Database Buffers 348127232 bytes Redo Buffers 5079040 bytes Database mounted. Database opened.
删除undo表空间
因为重新指定了undo表空间,所以我们可以将undotbs1这个表空间删除
SQL> drop tablespace undotbs1 including CONTENTS;
重建表空间
CREATE SMALLFILE UNDO TABLESPACE UNDOTBS1 DATAFILE 'C:\app\administrator\oradata\ora11r2\UNDOTBS01.DBF' SIZE 200M REUSE AUTOEXTEND ON NEXT 10M MAXSIZE 8G;
重新创建pfile
create pfile from spfile;
重启oracle数据库
PS:ORA-00600[4193]
Starting up: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options. Using parameter settings in server-side spfile D:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEPRJDB.ORA System parameters with non-default values: processes = 150 nls_language = "SIMPLIFIED CHINESE" nls_territory = "CHINA" memory_target = 1232M control_files = "D:\ORACLE\ORADATA\PRJDB\CONTROL01.CTL" control_files = "D:\ORACLE\FLASH_RECOVERY_AREA\PRJDB\CONTROL02.CTL" db_block_size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "d:\oracle\flash_recovery_area" db_recovery_file_dest_size= 3852M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=prjdbXDB)" audit_file_dest = "D:\ORACLE\ADMIN\PRJDB\ADUMP" audit_trail = "DB" db_name = "prjdb" open_cursors = 300 deferred_segment_creation= FALSE diagnostic_dest = "D:\ORACLE" Wed Jun 11 10:43:02 2014 PMON started with pid=2, OS id=3868 Wed Jun 11 10:43:02 2014 VKTM started with pid=3, OS id=2484 at elevated priority VKTM running at (10)millisec precision with DBRM quantum (100)ms Wed Jun 11 10:43:02 2014 GEN0 started with pid=4, OS id=2544 Wed Jun 11 10:43:02 2014 DIAG started with pid=5, OS id=2376 Wed Jun 11 10:43:02 2014 DBRM started with pid=6, OS id=3264 Wed Jun 11 10:43:02 2014 PSP0 started with pid=7, OS id=3936 Wed Jun 11 10:43:02 2014 DIA0 started with pid=8, OS id=3836 Wed Jun 11 10:43:02 2014 MMAN started with pid=9, OS id=2688 Wed Jun 11 10:43:02 2014 DBW0 started with pid=10, OS id=708 Wed Jun 11 10:43:02 2014 LGWR started with pid=11, OS id=3716 Wed Jun 11 10:43:02 2014 CKPT started with pid=12, OS id=492 Wed Jun 11 10:43:02 2014 SMON started with pid=13, OS id=1324 Wed Jun 11 10:43:02 2014 RECO started with pid=14, OS id=1828 Wed Jun 11 10:43:02 2014 MMON started with pid=15, OS id=3672 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... Wed Jun 11 10:43:02 2014 MMNL started with pid=16, OS id=3908 starting up 1 shared server(s) ... ORACLE_BASE from environment = d:\oracle Wed Jun 11 10:43:02 2014 alter database mount exclusive Successful mount of redo thread 1, with mount id 1302693302 Database mounted in Exclusive Mode Lost write protection disabled Completed: alter database mount exclusive alter database open Beginning crash recovery of 1 threads parallel recovery started with 2 processes Started redo scan Completed redo scan read 34 KB redo, 20 data blocks need recovery Started redo application at Thread 1: logseq 4145, block 3 Recovery of Online Redo Log: Thread 1 Group 2 Seq 4145 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO02.LOG Completed redo application of 0.02MB Completed crash recovery at Thread 1: logseq 4145, block 71, scn 176123270 20 data blocks read, 20 data blocks written, 34 redo k-bytes read Wed Jun 11 10:43:14 2014 Thread 1 advanced to log sequence 4146 (thread open) Thread 1 opened at log sequence 4146 Current log# 3 seq# 4146 mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Successful open of redo thread 1 Wed Jun 11 10:43:15 2014 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Wed Jun 11 10:43:15 2014 SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is US7ASCII Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_smon_1324.trc (incident=69779): ORA-00600: ??????, ??: [4194], [], [ Incident details in: d:\oracle\diag\rdbms\prjdb\prjdb\incident\incdir_69779\prjdb_smon_1324_i69779.trc No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Wed Jun 11 10:43:19 2014 Trace dumping is performing id=[cdmp_20140611104319] Doing block recovery for file 3 block 502 Resuming block recovery (PMON) for file 3 block 502 Block recovery from logseq 4146, block 63 to scn 176123517 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery stopped at EOT rba 4146.73.16 Block recovery completed at rba 4146.73.16, scn 0.176123515 Doing block recovery for file 3 block 240 Resuming block recovery (PMON) for file 3 block 240 Block recovery from logseq 4146, block 63 to scn 176123507 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.69.16, scn 0.176123509 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_smon_1324.trc: ORA-01595: ??? (2) ??? (8) ??? ORA-00600: ??????, ??: [4194], [], [ Starting background process QMNC Wed Jun 11 10:43:22 2014 QMNC started with pid=22, OS id=2124 Wed Jun 11 10:43:23 2014 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=69795): ORA-00600: ??????, ??: [4193], [], [ Incident details in: d:\oracle\diag\rdbms\prjdb\prjdb\incident\incdir_69795\prjdb_mmon_3672_i69795.trc Completed: alter database open Trace dumping is performing id=[cdmp_20140611104326] Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery stopped at EOT rba 4146.77.16 Block recovery completed at rba 4146.77.16, scn 0.176123527 Doing block recovery for file 3 block 272 Resuming block recovery (PMON) for file 3 block 272 Block recovery from logseq 4146, block 73 to scn 176123520 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.73.16, scn 0.176123521 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=69796): ORA-00600: ??????, ??: [4193], [: ?? Incident details in: d:\oracle\diag\rdbms\prjdb\prjdb\incident\incdir_69796\prjdb_mmon_3672_i69796.trc Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=69797): ORA-00600: ??????, ??: [4193], [], [ Incident details in: d:\oracle\diag\rdbms\prjdb\prjdb\incident\incdir_69797\prjdb_mmon_3672_i69797.trc Wed Jun 11 10:43:33 2014 Trace dumping is performing id=[cdmp_20140611104333] Wed Jun 11 10:43:34 2014 Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=69798): ORA-00600: ??????, ??: [4193], [], [ Incident details in: d:\oracle\diag\rdbms\prjdb\prjdb\incident\incdir_69798\prjdb_mmon_3672_i69798.trc Trace dumping is performing id=[cdmp_20140611104335] Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Trace dumping is performing id=[cdmp_20140611104337] Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=69799): ORA-00600: ??????, ??: [4193], [], [ Incident details in: d:\oracle\diag\rdbms\prjdb\prjdb\incident\incdir_69799\prjdb_mmon_3672_i69799.trc Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=69800): ORA-00600: ??????, ??: [4193], [], [ Trace dumping is performing id=[cdmp_20140611104339] Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=69801): ORA-00600: ??????, ??: [4193], [], [ Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=69802): ORA-00600: ??????, ??: [4193], [], [ Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=70876): ORA-00600: ??????, ??: [4193], [], [ Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=70877): ORA-00600: ??????, ??: [4193], [], [ Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=70878): ORA-00600: ??????, ??: [4193], [], [ Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_mmon_3672.trc (incident=70879): ORA-00600: ??????, ??: [4193], [], [ Wed Jun 11 10:43:46 2014 Doing block recovery for file 3 block 5380 Resuming block recovery (PMON) for file 3 block 5380 Block recovery from logseq 4146, block 73 to scn 176123528 Recovery of Online Redo Log: Thread 1 Group 3 Seq 4146 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\PRJDB\REDO03.LOG Block recovery completed at rba 4146.77.16, scn 0.176123530 Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_pmon_3868.trc (incident=69691): ORA-00600: ??????, ??: [4193], [], [ Errors in file d:\oracle\diag\rdbms\prjdb\prjdb\trace\prjdb_pmon_3868.trc: ORA-00600: ??????, ??: [4193], [], [ PMON (ospid: 3868): terminating the instance due to error 472
从这里可以看到出现了ORA-600[4194]/[4193],第一感觉就是undo出现问题。
4193:表示undo和redo不一致(Arg [a] Undo record seq number,Arg [b] Redo record seq number );
4194:表示也是undo和redo不一致(Arg [a] Maximum Undo record number in Undo block,Arg [b] Undo record number from Redo block)
所以出现4193错误,解决方法跟4194一样。
[转帖]oracle 00600 4194 4193 问题的处理的更多相关文章
- UNDO表空间损坏,爆满,ORA-600[4194]/[4193]错误解决
模拟手工删除UNDO表空间 在ORADATA 中把UNDOTBS01.DBF 删除 模拟启库 SQL> STARUP; * 第 1 行出现错误: ORA-01157: 无法标识/锁定数据文件 2 ...
- [转帖]Oracle 补丁体系(PSR/PSU/CPU) 及 opatch 工具 介绍
Oracle 补丁体系(PSR/PSU/CPU) 及 opatch 工具 介绍 原文:http://blog.csdn.net/tianlesoftware/article/details/58095 ...
- [转帖]Oracle 各个版本的升级路线图
从oracle 7开始(甚至更早版本)到oracle 9iR2. 来源: https://blog.csdn.net/cymm_liu/article/details/11647533 http:// ...
- [转帖]Oracle 12cR2使用经验
大规模升级来临,谈谈Oracle 12cR2使用经验 随着2019年2月13日,Oracle 19c (Oracle 12.2.0.3) for Exadata 版本发布,Oracle 12cR2体系 ...
- [转帖]Oracle 裁员史:技术人死于重组,卒于云计算
Oracle 裁员史:技术人死于重组,卒于云计算 https://www.infoq.cn/article/tm-mcdHCPCI4eEwr6dbY 大厂裁员 我妈妈也总担心我没工作了 怎么还房贷 田 ...
- [转帖]oracle改版sql server问题点汇总
https://www.cnblogs.com/zhangdk/p/oracle_sqlserver.html 只记得 最开始的时候看过 没有具体的了解里面的特点 原作者总结的很好 留下来 以后说不定 ...
- 转帖 Oracle 主键的处理方法 http://www.cnblogs.com/Richardzhu/p/3470929.html
Oracle之主键的创建.添加.删除操作 一.创建表的同时创建主键约束 1.1.无命名 SQL> create table jack (id int primary key not null ...
- [转帖]Oracle 11G RAC For Windows 2008 R2部署手册
Oracle 11G RAC For Windows 2008 R2部署手册(亲测,成功实施多次) https://www.cnblogs.com/yhfssp/p/7821593.html 总体规划 ...
- [转帖] Oracle数据库 通过触发器 限制登录ip
转帖 From https://yq.aliyun.com/ziliao/123360 create or replace trigger logon_ip_control after logon o ...
随机推荐
- web前端_DOM操作
DOM(Document Object Model 文档对象模型) 一个web页面的展示,是由html标签组合成的一个页面,dom对象实际就是将html标签转换成了一个文档对象.可以通过dom对象中j ...
- 13、Qt界面布局
为了使设计的界面与运行后显示的一致,在main.cpp中添加代码,放在QApplication a(argc, argv);之前 #if (QT_VERSION >= QT_VERSION_CH ...
- 2-SAT (two-statisfiability) 算法 学习笔记
$2-SAT$问题指的是对于若干限制求出一组可行解的问题. 考虑对于$n$个值域为${0,1}$的变量$x_1 , x_2 ,...,x_n$ 满足若干限制: 若 $x_i = p$ 则 $x_j = ...
- 安装MongoDB到CentOS 6
MongoDB是一个面向海量文档存数据动态存储的NoSQL型数据库.是一个除了用于关系型数据库如MySQL,PostgreSQL数据库表格的格式,和微软SQL以外的一种数据模型存储形式.他的功能包括了 ...
- Unity3D_(API)Random随机数
Unity随机数Random官方文档: 传送门 一.生成一个随机数 二.Random.InitState()生成伪随机数 三.官方文档中常用的方法 创建一个Cube用来挂载Random_Gary.cs ...
- avue你繁琐的表格、表单、树等组件开发的解脱工具,了解一下?
简介 Avue是基于Vue.js和element的快速开发框架 它的核心是数据驱动UI的思想,让我们从繁琐的crud开发中解脱出来,它的写法类似easyUI,但是写起来比easyui更容易,因为它是基 ...
- mongo 生命周期
监听MongoDB的生命周期,只需重写org.springframework.data.mongodb.core.mapping.event.AbstractMongoEventListener的子类 ...
- SQLite索引
索引(Index)是一种特殊的查找表,数据库搜索引擎用来加快数据检索.简单地说,索引是一个指向表中数据的指针.一个数据库中的索引与一本书后边的索引是非常相似的. 例如,如果您想在一本讨论某个话题的书中 ...
- shiro.ini
# # Licensed to the Apache Software Foundation (ASF) under one # or more contributor license agreeme ...
- yconsole使用说明
介绍: yconsole是yhd用于管理缓存的工具(python实现),它的主要功能是为各个应用分配和管理缓存,以及错误修复.和它配合使用的还有ycache-client.yagent.zookeep ...