Oracle 联机重做日志文件恢复(redo log)
非当前联机日志文件故障恢复 1.启动数据库时遇到ORA-00313,ORA-00312错误。 ORA-00313: open failed for members of log group
非当前联机日志文件故障恢复
1.启动数据库时遇到ORA-00313,ORA-00312错误。
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/home/Oracle/oradata/s1/redo01.log'
2.查看v$log视图。
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ---------
1 1 11 52428800 1 YES INACTIVE 489912 09-NOV-12
3 1 10 52428800 1 YES INACTIVE 488868 08-NOV-12
2 1 12 52428800 1 NO CURRENT 519028 11-NOV-12
3.用clear命令重建该日志文件
如果该日志文件已经归档则:
SQL> alter database clear logfile group 1;
Database altered.
如果该日志文件还没有归档则:
SQL> alter database clear unarchived logfile group 3;
Database altered.
4.打开数据库,重新备份数据库(建议clear,特别是clear unarchived后做一次全备份)
SQL> alter database open;
Database altered.
当前联机日志文件故障恢复
归档模式下,当前日志文件损坏有两种情况
一、数据库正常关闭,日志文件中没有解决的事务要实例恢复,当前日志组的损坏可直接用户
alter database clear unarchived logfile group n来重建
二、日志文件中有活动事物,数据库需要介质恢复,有两种补救方法
a、在归档模式下,有可用备份
b、无可用备份,通过强制性恢复,但可能会导致数据库不一致
a.在归档模式下有可用备份(不完全恢复)
1.1.启动数据库时报错,并用v$log查看
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/home/oracle/oradata/s1/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ---------
1 1 16 52428800 1 NO CURRENT 520744 11-NOV-12
2 1 15 52428800 1 YES ACTIVE 520712 11-NOV-12
3 1 14 52428800 1 YES INACTIVE 520705 11-NOV-12
2.试用clear恢复
SQL> alter database clear logfile group 1;
SQL> alter database clear unarchived logfile group 1;
alter database clear unarchived logfile group 1
*
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of instance s1 (thread 1)
ORA-00312: online log 1 thread 1: '/home/oracle/oradata/s1/redo01.log'
3.执行recover database until cancel先用户auto后用cancel,报错如下:
SQL> recover database until cancel;
ORA-00279: change 520744 generated at 11/11/2012 22:43:39 needed for thread 1
ORA-00289: suggestion : /archive1/1_16_798842981.dbf
ORA-00280: change 520744 for thread 1 is in sequence #16
Specify log: {
auto
ORA-00308: cannot open archived log '/archive1/1_16_798842981.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log '/archive1/1_16_798842981.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/home/oracle/oradata/s1/system01.dbf'
SQL> recover database until cancel;
ORA-00279: change 520744 generated at 11/11/2012 22:43:39 needed for thread 1
ORA-00289: suggestion : /archive1/1_16_798842981.dbf
ORA-00280: change 520744 for thread 1 is in sequence #16
Specify log: {
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/home/oracle/oradata/s1/system01.dbf'
ORA-01112: media recovery not started
4.在rman下restore database;
RMAN> restore database;
5.在rman下recover database:报错如下:
RMAN> recover database;
Starting recover at 11-NOV-12
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/11/2012 22:54:15
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/home/oracle/oradata/s1/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3

热AI工具

Undresser.AI Undress
人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover
用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool
免费脱衣服图片

Clothoff.io
AI脱衣机

Video Face Swap
使用我们完全免费的人工智能换脸工具轻松在任何视频中换脸!

热门文章

热工具

记事本++7.3.1
好用且免费的代码编辑器

SublimeText3汉化版
中文版,非常好用

禅工作室 13.0.1
功能强大的PHP集成开发环境

Dreamweaver CS6
视觉化网页开发工具

SublimeText3 Mac版
神级代码编辑软件(SublimeText3)

在CentOS系统上搭建Hadoop分布式文件系统(HDFS)需要多个步骤,本文提供一个简要的配置指南。一、前期准备安装JDK:在所有节点上安装JavaDevelopmentKit(JDK),版本需与Hadoop兼容。可从Oracle官网下载安装包。环境变量配置:编辑/etc/profile文件,设置Java和Hadoop的环境变量,使系统能够找到JDK和Hadoop的安装路径。二、安全配置:SSH免密登录生成SSH密钥:在每个节点上使用ssh-keygen命令

vProcesserazrabotkiveb被固定,мнелостольностьстьс粹馏标д都LeavallySumballanceFriablanceFaumDoptoMatification,Čtookazalovnetakprosto,kakaožidal.posenesko

Redis缓存方案如何实现产品排行榜列表的需求?在开发过程中,我们常常需要处理排行榜的需求,例如展示一个�...

在CentOS系统上启用Redis慢查询日志,提升性能诊断效率。以下步骤将指导您完成配置:第一步:定位并编辑Redis配置文件首先,找到Redis配置文件,通常位于/etc/redis/redis.conf。使用以下命令打开配置文件:sudovi/etc/redis/redis.conf第二步:调整慢查询日志参数在配置文件中,找到并修改以下参数:#慢查询阈值(毫秒)slowlog-log-slower-than10000#慢查询日志最大条目数slowlog-max-len

在CentOS上配置Hadoop分布式文件系统(HDFS)时,需要修改以下关键配置文件:core-site.xml:fs.defaultFS:指定HDFS的默认文件系统地址,例如hdfs://localhost:9000。hadoop.tmp.dir:指定Hadoop临时文件的存储目录。hadoop.proxyuser.root.hosts和hadoop.proxyuser.ro

SpringBoot中使用Redis缓存OAuth2Authorization对象在SpringBoot应用中,使用SpringSecurityOAuth2AuthorizationServer...

CentOS系统下HDFS配置错误排查指南本文旨在帮助您解决CentOS系统中配置HDFS时遇到的问题。请按照以下步骤进行排查:Java环境验证:确认JAVA_HOME环境变量已正确设置。在/etc/profile或~/.bashrc文件中添加以下内容:exportJAVA_HOME=/path/to/your/javaexportPATH=$JAVA_HOME/bin:$PATH执行source/etc/profile或source~/.bashrc使配置生效。Hadoop

在CentOS系统上安装和配置GitLab时,数据库的选择至关重要。GitLab兼容多种数据库,但PostgreSQL和MySQL(或MariaDB)最为常用。本文将分析数据库选择因素,并提供详细的安装和配置步骤。数据库选择指南选择数据库需要考虑以下因素:PostgreSQL:GitLab的默认数据库,功能强大,可扩展性高,支持复杂查询和事务处理,适合大型应用场景。MySQL/MariaDB:广泛应用于Web应用的流行关系型数据库,性能稳定可靠。MongoDB:NoSQL数据库,擅长处
