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脱衣机

AI Hentai Generator
免费生成ai无尽的。

热门文章

热工具

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

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

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

Dreamweaver CS6
视觉化网页开发工具

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

热门话题

使用PHP的cURL库发送JSON数据在PHP开发中,经常需要与外部API进行交互,其中一种常见的方式是使用cURL库发送POST�...

在Docker环境中使用PECL安装扩展时报错的原因及解决方法在使用Docker环境时,我们常常会遇到一些令人头疼的问�...

本文介绍在Debian系统下监控PostgreSQL数据库的多种方法和工具,助您全面掌握数据库性能监控。一、利用PostgreSQL内置监控视图PostgreSQL自身提供多个视图用于监控数据库活动:pg_stat_activity:实时展现数据库活动,包括连接、查询和事务等信息。pg_stat_replication:监控复制状态,尤其适用于流复制集群。pg_stat_database:提供数据库统计信息,例如数据库大小、事务提交/回滚次数等关键指标。二、借助日志分析工具pgBadg

提升DebianHadoop集群性能,需要从硬件、软件、资源管理和性能调优等多个方面入手。以下是一些关键的优化策略和建议:一、硬件与系统配置精挑细选硬件配置:根据实际应用场景选择合适的CPU、内存和存储设备。SSD加速I/O:尽可能使用固态硬盘(SSD)提升I/O操作速度。内存扩容:为NameNode和DataNode节点分配充足的内存,以应对更大规模的数据处理和任务。二、软件配置优化Hadoop配置文件调整:core-site.xml:配置HDFS默认文件系统

Go语言中使用RedisStream实现消息队列时类型转换问题在使用Go语言与Redis...

深入探讨console.log输出差异的根源本文将分析一段代码中console.log函数输出结果的差异,并解释其背后的原因。�...
