ORA-00742 ORA-00312 恢复---惜分飞

news2024/11/29 0:31:00

有客户反馈,断电之后数据库启动报ORA-00742和ORA-00312,无法正常open
 

ORA-742-ORA-312


我们远程上去尝试open库结果也报同样错误

[oracle@oldhis oradata]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Wed Apr 10 09:40:03 2024

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> recover database;

Media recovery complete.

SQL> alter database open;

alter database open

*

ERROR at line 1:

ORA-00742: Log read detects lost write in thread %d sequence %d block %d

ORA-00312: online log 3 thread 1: '/oradata/shrdh/redo03.log'

SQL> select group#,status from v$log;

    GROUP# STATUS

---------- ----------------

         1 INACTIVE

         3 CURRENT

         2 INACTIVE

因为recover已经成功,但是依旧报ORA-742错误,尝试查询scn相关信息

SQL> set pages 10000

set numw 16

SELECT status,

checkpoint_change#,

checkpoint_time,last_change#,

count(*) ROW_NUM

FROM v$datafile

GROUP BY status, checkpoint_change#, checkpoint_time,last_change#

ORDER BY status, checkpoint_change#, checkpoint_time;

set numw 16

col CHECKPOINT_TIME for a40

set lines 150

set pages 1000

SELECT status,

to_char(checkpoint_time,'yyyy-mm-dd hh24:mi:ss') checkpoint_time,FUZZY,checkpoint_change#,

count(*) ROW_NUM

FROM v$datafile_header

GROUP BY status, checkpoint_change#, to_char(checkpoint_time,'yyyy-mm-dd hh24:mi:ss'),fuzzy

ORDER BY status, checkpoint_change#, checkpoint_time;

SQL> SQL>   2    3    4    5    6    7 

STATUS  CHECKPOINT_CHANGE# CHECKPOIN     LAST_CHANGE#          ROW_NUM

------- ------------------ --------- ---------------- ----------------

ONLINE          1279351848 26-MAR-24       1279351848               19

SYSTEM          1279351848 26-MAR-24       1279351848                1

SQL> SQL> SQL> SQL> SQL> SQL> SQL>   2    3    4    5    6 

STATUS  CHECKPOINT_TIME                          FUZ CHECKPOINT_CHANGE#          ROW_NUM

------- ---------------------------------------- --- ------------------ ----------------

ONLINE  2024-03-26 00:05:45                      NO          1279351848               20

基于这样的情况,我们判断数据库直接open成功

SQL> recover database using backup controlfile;

ORA-00279: change 1279351848 generated at 03/26/2024 00:05:45 needed for thread 1

ORA-00289: suggestion : /oradata/arch/shrdh/shrdh_1_12984_974767526.arc

ORA-00280: change 1279351848 for thread 1 is in sequence #12984

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

/oradata/shrdh/redo03.log

Log applied.

Media recovery complete.

SQL> alter database open resetlogs;

Database altered.

后面比较不幸,数据库报ORA-600 4194错误导致数据库异常

Wed Apr 10 09:43:08 2024

ALTER DATABASE RECOVER  database using backup controlfile 

Media Recovery Start

 started logmerger process

Parallel Media Recovery started with 4 slaves

ORA-279 signalled during: ALTER DATABASE RECOVER  database using backup controlfile  ...

Wed Apr 10 09:43:24 2024

ALTER DATABASE RECOVER    LOGFILE '/oradata/shrdh/redo03.log' 

Media Recovery Log /oradata/shrdh/redo03.log

Media Recovery Complete (shrdh)

Completed: ALTER DATABASE RECOVER    LOGFILE '/oradata/shrdh/redo03.log' 

alter database open resetlogs

RESETLOGS after complete recovery through change 1279351849

Clearing online redo logfile 1 /oradata/shrdh/redo01.log

Clearing online log 1 of thread 1 sequence number 12982

Clearing online redo logfile 1 complete

Clearing online redo logfile 2 /oradata/shrdh/redo02.log

Clearing online log 2 of thread 1 sequence number 12983

Clearing online redo logfile 2 complete

Clearing online redo logfile 3 /oradata/shrdh/redo03.log

Clearing online log 3 of thread 1 sequence number 12984

Clearing online redo logfile 3 complete

Resetting resetlogs activation ID 1820377766 (0x6c80c2a6)

Online log /oradata/shrdh/redo01.log: Thread 1 Group 1 was previously cleared

Online log /oradata/shrdh/redo02.log: Thread 1 Group 2 was previously cleared

Online log /oradata/shrdh/redo03.log: Thread 1 Group 3 was previously cleared

Wed Apr 10 09:43:34 2024

Setting recovery target incarnation to 2

Wed Apr 10 09:43:34 2024

Assigning activation ID 2011515185 (0x77e54931)

Thread 1 opened at log sequence 1

  Current log# 1 seq# 1 mem# 0: /oradata/shrdh/redo01.log

Successful open of redo thread 1

Wed Apr 10 09:43:34 2024

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Wed Apr 10 09:43:34 2024

SMON: enabling cache recovery

[25089] Successfully onlined Undo Tablespace 2.

Undo initialization finished serial:0 start:1273646224 end:1273646494 diff:270 (2 seconds)

Dictionary check beginning

Dictionary check complete

Verifying file header compatibility for 11g tablespace encryption..

Verifying 11g file header compatibility for tablespace encryption completed

SMON: enabling tx recovery

Database Characterset is ZHS16GBK

No Resource Manager plan active

replication_dependency_tracking turned off (no async multimaster replication found)

Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_smon_21704.trc  (incident=84296):

ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []

Incident details in: /u01/app/oracle/diag/rdbms/shrdh/shrdh/incident/incdir_84296/shrdh_smon_21704_i84296.trc

Use ADRCI or Support Workbench to package the incident.

See Note 411.1 at My Oracle Support for error and packaging details.

Starting background process QMNC

Wed Apr 10 09:43:35 2024

QMNC started with pid=24, OS id=25340

LOGSTDBY: Validating controlfile with logical metadata

LOGSTDBY: Validation complete

Block recovery from logseq 1, block 61 to scn 1279351933

Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0

  Mem# 0: /oradata/shrdh/redo01.log

Block recovery stopped at EOT rba 1.99.16

Block recovery completed at rba 1.99.16, scn 0.1279351933

Block recovery from logseq 1, block 61 to scn 1279351919

Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0

  Mem# 0: /oradata/shrdh/redo01.log

Block recovery completed at rba 1.87.16, scn 0.1279351922

Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_smon_21704.trc:

ORA-01595: error freeing extent (2) of rollback segment (7))

ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []

Completed: alter database open resetlogs

Wed Apr 10 09:43:37 2024

Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_m000_25343.trc  (incident=84392):

ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []

Incident details in: /u01/app/oracle/diag/rdbms/shrdh/shrdh/incident/incdir_84392/shrdh_m000_25343_i84392.trc

Use ADRCI or Support Workbench to package the incident.

See Note 411.1 at My Oracle Support for error and packaging details.

Wed Apr 10 09:43:37 2024

Starting background process CJQ0

Wed Apr 10 09:43:37 2024

CJQ0 started with pid=29, OS id=25357

Starting background process SMCO

Wed Apr 10 09:43:37 2024

SMCO started with pid=30, OS id=25360

Wed Apr 10 09:43:38 2024

Flush retried for xcb 0x115b42d28, pmd 0x1148dea70

Block recovery from logseq 1, block 61 to scn 1279351933

Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0

  Mem# 0: /oradata/shrdh/redo01.log

Block recovery completed at rba 1.99.16, scn 0.1279351934

Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_pmon_21679.trc  (incident=84208):

ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []

Incident details in: /u01/app/oracle/diag/rdbms/shrdh/shrdh/incident/incdir_84208/shrdh_pmon_21679_i84208.trc

Use ADRCI or Support Workbench to package the incident.

See Note 411.1 at My Oracle Support for error and packaging details.

Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_pmon_21679.trc:

ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []

PMON (ospid: 21679): terminating the instance due to error 472

Wed Apr 10 09:43:47 2024

Instance terminated by PMON, pid = 21679

报错比较明显,对undo进行处理即可.

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.coloradmin.cn/o/1599122.html

如若内容造成侵权/违法违规/事实不符,请联系多彩编程网进行投诉反馈,一经查实,立即删除!

相关文章

计算机网络(五)传输层

传输层 从通信和信息处理的角度看&#xff0c;传输层向它上面的应用层提供通信服务&#xff0c;属于面向通信部分的最高层&#xff0c;同时也是用户功能中的最低层 传输层功能&#xff1a; 传输层提供应用进程之间的逻辑通信(即端到端的通信)。与网络层的区别区别是&#xf…

MySQL 试图

视图功能在 5.0 以后的版本启用 视图是一张虚表。数据表确实包含了具体数据并且保存到硬盘中的实表。视图使用数据检索语句动态生 成的一张虚表。每一次数据服务重启或者系统重启之后&#xff0c;在数据库服务启动期间&#xff0c;会使用创建视图的语 句重新生成视图中的数据&…

揭秘智慧礼品背后的故事

如若不是从事技术行业&#xff0c;在罗列礼品清单时&#xff0c;可能不会想到 “数据”&#xff0c;但幸运的是&#xff0c;我们想到了。如何将AI技术应用到当季一些最受青睐的产品中去&#xff0c;训练数据是这一智能技术的背后动力。很多电子设备或名称中带有“智能”一词的设…

频率域滤波总结

我本来想写在一起的&#xff0c;但是这样的话就没有重点了。分开写更能总结出来问题。这里的步骤5的对称滤波函数确实是(2M-1)x(2N-1)的大小&#xff0c;但是书上还说了如下图所示的问题: 首先第一个问题是乘积的问题&#xff0c;为什么普通的函数乘积也需要填充零&#xff1f;…

【电控笔记6.2】拉式转换与转移函数

概要 laplace&#xff1a;单输入单输出&#xff0c;线性系统 laplace 传递函数 总结

DNS解析实验

一、DNS正向解析实验 准备工作 服务端及客户端都关闭安全软件 [rootserver ~]# setenforce 0 [rootserver ~]# systemctl stop firewalld服务端安装bind软件 [rootserver ~]# yum install bind -y服务端配置静态IP [rootserver ~]# nmcli c modify ens33 ipv4.m…

浅尝一下ECS(Entity Component System)(学习笔记)

参考文章&#xff1a;浅谈Unity ECS&#xff08;一&#xff09;Uniy ECS基础概念介绍&#xff1a;面向未来的ECS - 知乎 (zhihu.com) 视频链接&#xff1a;【青幻译制】GDC讲座系列之三 守望先锋的游戏架构和网络代码_哔哩哔哩_bilibili 云风的 BLOG: 浅谈《守望先锋》中的 E…

消息队列和分布式消息队列

文章目录 分析系统现状不足中间件消息队列什么是消息队列&#xff1f;应用场景消息队列的模型为什么不直接传输&#xff0c;而要用消息队列&#xff1f;为什么要用消息队列&#xff1f;消息队列的缺点&#xff1f; 分布式消息队列分布式消息队列的优势&#xff1f;消息队列应用…

PLC远程通信:实现工业自动化的关键技术

在当今高度信息化和自动化的时代&#xff0c;工业领域对于实时数据的准确传输和迅速响应提出了更高要求。而PLC(可编程逻辑控制器)远程通信技术&#xff0c;正是能够实现工业自动化的关键技术之一。 首先&#xff0c;我们需要了解PLC远程通信的原理。PLC作为一种专用计算机控制…

设计模式代码实战-组合模式

1、问题描述 小明所在的公司内部有多个部门&#xff0c;每个部门下可能有不同的子部门或者员工。 请你设计一个组合模式来管理这些部门和员工&#xff0c;实现对公司组织结构的统一操作。部门和员工都具有一个通用的接口&#xff0c;可以获取他们的名称以及展示公司组织结构。…

学习BOM

目录 前言: 1. BOM组成&#xff1a; 1.1Window 对象&#xff1a; 1.1Location 对象&#xff1a; 1.2Navigator 对象&#xff1a; 1.2.1 navigator 对象包含了关于浏览器的信息包括&#xff1a; 1.3History 对象&#xff1a; 1.4常用的history的方法和属性: 1.4Document…

氟化钙与盐酸反应

结论&#xff1a;可以反应 参考链接 为什么盐酸,硝酸不能溶解氟化钙呢?氢氟酸可是弱酸啊。。。_百度知道 (baidu.com)https://zhidao.baidu.com/question/421110040.html特此记录 anlog 2024年4月16日

中医圆运动规律

目录 人体圆运动营气在十二经脉的运行规律子午流注与圆运动升降结合图 人体圆运动 营气在十二经脉的运行规律 营气在脉中&#xff0c;卫气在脉外 这个顺序也是子午流注的顺序 子午流注与圆运动升降结合图

【论文阅读02】一种基于双通道的水下图像增强卷积神经网络

来源&#xff1a;海洋论坛▏一种基于双通道的水下图像增强卷积神经网络 当前不会的 一、背景&#xff1a; 水下图像增强方法包含有无水下成像模型的水下图像增强方法、基于水下成像模型的水下图像恢复方法、水下成像模型与深度学习相结合的方法以及完全采用深度学习的方…

数据结构与算法——22.哈希算法

这篇文章我们来讲一下哈希表中较为关键的部分——哈希算法 目录 1.哈希算法的介绍 2.hash算法的使用 2.1 Object.hashCode 2.2 String.hashCode 3.关于哈希表及哈希算法的一些思考 1.哈希算法的介绍 问题&#xff1a;什么是哈希算法&#xff1f;哈希算法有哪些&#xff…

【算法一则】做算法学数据结构 - 简化路径 - 【栈】

目录 题目栈代码题解 题目 给你一个字符串 path &#xff0c;表示指向某一文件或目录的 Unix 风格 绝对路径 &#xff08;以 ‘/’ 开头&#xff09;&#xff0c;请你将其转化为更加简洁的规范路径。 在 Unix 风格的文件系统中&#xff0c;一个点&#xff08;.&#xff09;表…

兔C_Java集:Java 语言简介

文章目录 1. Java简介历史简介问&#xff1a;Oracle 为什么收购 SUN 公司关于三个分支语言特性&#xff1a; 2. JDK 的安装与配置安装的官网链接配置环境变量 3. 第一个Java程序4. 第一个程序解释关于类的定义 5. CLASSPATH命令自动配置CLASSPATH 与 JVM 的关系CLASSPATH 的手动…

OM3 与 OM4:主要区别和实际应用

OM3 和 OM4 都是激光优化的多模光纤&#xff0c;具有 50/125μm 光纤芯&#xff0c;专为满足 ISO 11801 标准而开发。它们在光纤连接器和应用场景上具有相似性&#xff0c;这往往会导致用户之间的混淆。这些光纤主要设计用于数据中心、局域网 &#xff08;LAN&#xff09; 和其…

500以内的不入耳运动耳机推荐,首推五大业内顶级优品

不入耳式运动耳机因其独特的佩戴方式和设计&#xff0c;能够在运动过程中保持对周围环境的警觉&#xff0c;避免因音乐沉浸而忽视潜在的安全隐患&#xff0c;同时它们还能有效减少对耳道的压迫&#xff0c;让运动更加舒适自在&#xff0c;接下来&#xff0c;就让我为大家推荐一…

MAC系统安装PHP、Java、Python、mysql、Composer等环境无权限问题的详细操作方法说明。

本篇文章主要讲解MAC系统安装PHP、Java、Python、mysql、Composer等环境无权限问题的详细操作方法说明。通过本篇文章你可以快速掌握brew安装相对应环境的能力。 作者&#xff1a;任聪聪 日期&#xff1a;2024年4月12日 一、brew介绍及安装说明 官网地址&#xff1a;https://b…