我的编程空间,编程开发者的网络收藏夹
学习永远不晚

OPEN RESETLOGS ,报ORA-00392 ORA-00312 in Oracle12c

短信预约 -IT技能 免费直播动态提醒
省份

北京

  • 北京
  • 上海
  • 天津
  • 重庆
  • 河北
  • 山东
  • 辽宁
  • 黑龙江
  • 吉林
  • 甘肃
  • 青海
  • 河南
  • 江苏
  • 湖北
  • 湖南
  • 江西
  • 浙江
  • 广东
  • 云南
  • 福建
  • 海南
  • 山西
  • 四川
  • 陕西
  • 贵州
  • 安徽
  • 广西
  • 内蒙
  • 西藏
  • 新疆
  • 宁夏
  • 兵团
手机号立即预约

请填写图片验证码后获取短信验证码

看不清楚,换张图片

免费获取短信验证码

OPEN RESETLOGS ,报ORA-00392 ORA-00312 in Oracle12c

【现象】

SQL> alter database open resetlogs;

alter database open resetlogs

*

ERROR at line 1:

ORA-00392: log 4 of thread 1 is being cleared, operation not allowed

ORA-00312: online log 4 thread 1: '/mnt/data/PBF/db/proddata/redo04a.log'

ORA-00312: online log 4 thread 1: '/mnt/data/PBF/db/proddata/redo04b.log'

 

【官方解释】

CLEARING_CURRENT - Current log is being cleared of a closed thread. The log can stay in this status if there is some failure in the switch such as an I/O error writing the new log header.

CLEARING - Log is being re-created as an empty log after an ALTER DATABASE CLEAR

【重做日志文件的集中状态】

1.CURRENT - 当前正在被LGWR使用的group(同时是ACTIVE状态),其中记载数据库中正在进行的更改,删除将导致恢复时数据丢失。

2.ACTIVE - 活动的日志文件状态,日志完成切换或等待检查点事件时都可能出于这种状态,不是CURRENT的日志但是实例恢复时是需要的,此时的日志有可能已经完成了归档,即将变成INACTIVE状态,或者日志文件在等待Checkpoint事件没有完成归档。

3.INACTIVE - 非活动的日志状态,此时的日志实例恢复时不再需要,可能已经归档。

4.UNUSED - 尚未记录change的空白日志组,一般会出现在add logfile, resetlogs打开数据库或者使用了clear logfile命令后。

5.CLEARING - 表示该组重做日志文件正在被ALTER DATABASE CLEAR LOGFILE语句重建中(重建后状态会变成unused)。

6.CLEARING_CURRENT - 表示该组重做日志文件重建时出现错误,出现对日志文件的I/O故障就会出现这种状态。

 

 

 

【解决方法】

SQL> select group#,bytes/1024/1024||'M',status from v$log;

 

    GROUP# BYTES/1024/1024||'M'

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

STATUS

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

         1 1000M

CLEARING

 

         2 1000M

CLEARING

 

         5 1000M

CLEARING

 

 

    GROUP# BYTES/1024/1024||'M'

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

STATUS

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

         4 1000M

CLEARING_CURRENT

 

         3 1000M

CLEARING

 

 

SQL>

SQL>

SQL>

SQL>  alter database clear logfile group 1;

 alter database clear logfile group 2;

 alter database clear logfile group 3;

 alter database clear logfile group 4;

 alter database clear logfile group 5;

 

Database altered.

 

SQL>

Database altered.

 

SQL>

Database altered.

 

SQL>

Database altered.

 

SQL>

Database altered.

 

SQL> col group# form 99

SQL>  col bytes form 99999999999

SQL>  col status form a20

SQL>   select group#,bytes/1024/1024||'M',status from v$log;

 

GROUP# BYTES/1024/1024||'M'                      STATUS

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

     1 1000M                                     UNUSED

     2 1000M                                     UNUSED

     5 1000M                                     UNUSED

     4 1000M                                     CURRENT

     3 1000M                                     UNUSED


alter database open resetlogs;

OK!

免责声明:

① 本站未注明“稿件来源”的信息均来自网络整理。其文字、图片和音视频稿件的所属权归原作者所有。本站收集整理出于非商业性的教育和科研之目的,并不意味着本站赞同其观点或证实其内容的真实性。仅作为临时的测试数据,供内部测试之用。本站并未授权任何人以任何方式主动获取本站任何信息。

② 本站未注明“稿件来源”的临时测试数据将在测试完成后最终做删除处理。有问题或投稿请发送至: 邮箱/279061341@qq.com QQ/279061341

OPEN RESETLOGS ,报ORA-00392 ORA-00312 in Oracle12c

下载Word文档到电脑,方便收藏和打印~

下载Word文档

猜你喜欢

ORA-38871: cannot enable flashback before open resetlogs after incomplete recovery. ORACLE 报错 故障修复 远

文档解释ORA-38871: cannot enable flashback before open resetlogs after incomplete recovery.Cause: To enable flashback on a
ORA-38871: cannot enable flashback before open resetlogs after incomplete recovery. ORACLE 报错 故障修复 远
2023-11-05

ORA-01588: must use RESETLOGS option for database open ORACLE 报错 故障修复 远程处理

文档解释ORA-01588: must use RESETLOGS option for database openCause: An earlier attempt to open the database with the
ORA-01588: must use RESETLOGS option for database open ORACLE 报错 故障修复 远程处理
2023-11-04

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open ORACLE 报错 故障修复 远程处理

文档解释ORA-01589: must use RESETLOGS or NORESETLOGS option for database openCause: Either incomplete or backup control
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open ORACLE 报错 故障修复 远程处理
2023-11-05

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORACLE 报错 故障修复 远程处理

文档解释ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error belowCause: Media recovery with one of the
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORACLE 报错 故障修复 远程处理
2023-11-04

ORA-01126: database must be mounted in this instance and not open in any instance ORACLE 报错 故障修复 远程处

文档解释ORA-01126: database must be mounted in this instance and not open in any instanceCause: ObviousAction:
ORA-01126: database must be mounted in this instance and not open in any instance ORACLE 报错 故障修复 远程处
2023-11-04

ORA-28388: database is not open in read/write mode ORACLE 报错 故障修复 远程处理

文档解释ORA-28388: database is not open in read/write modeCause: Database was not open in read/write mode and could not
ORA-28388: database is not open in read/write mode ORACLE 报错 故障修复 远程处理
2023-11-05

ORA-15091: operation incompatible with open handle in this session ORACLE 报错 故障修复 远程处理

文档解释ORA-15091: operation incompatible with open handle in this sessionCause: The current session contained an open
ORA-15091: operation incompatible with open handle in this session ORACLE 报错 故障修复 远程处理
2023-11-05

ORA-10456: cannot open standby database; media recovery session may be in progress ORACLE 报错 故障修复 远程

文档解释ORA-10456: cannot open standby database; media recovery session may be in progressCause: A media recovery, RMAN, or
ORA-10456: cannot open standby database; media recovery session may be in progress ORACLE 报错 故障修复 远程
2023-11-05

ORA-39710: only connect AS SYSDBA is allowed when OPEN in UPGRADE mode ORACLE 报错 故障修复 远程处理

文档解释ORA-39710: only connect AS SYSDBA is allowed when OPEN in UPGRADE modeCause: An attempt was made to connect to a
ORA-39710: only connect AS SYSDBA is allowed when OPEN in UPGRADE mode ORACLE 报错 故障修复 远程处理
2023-11-05

ORA-22292: Cannot open a LOB in read-write mode without a transaction ORACLE 报错 故障修复 远程处理

文档解释ORA-22292: Cannot open a LOB in read-write mode without a transactionCause: An attempt was made to open a LOB in
ORA-22292: Cannot open a LOB in read-write mode without a transaction ORACLE 报错 故障修复 远程处理
2023-11-05

ORA-01138: database must either be open in this instance or not at all ORACLE 报错 故障修复 远程处理

文档解释ORA-01138: database must either be open in this instance or not at allCause: The requested operation can not be
ORA-01138: database must either be open in this instance or not at all ORACLE 报错 故障修复 远程处理
2023-11-05

编程热搜

目录