The ora-00392ora-00312 log is clearing the fault _oracle

Recently, when you restored the Oracle database open, you encountered Ora-00392:log 3 of thread 1 is being cleared, operation not allowed, which literally means that the log files are being purged and operations are not allowed.

Normally, when we are based on incomplete recovery, the log file needs to be emptied, and this time it is being emptied. Not very good understanding AH. Here is the solution to this problem.

First, the phenomenon of failure

 <code class= "Hljs VHDL" >SQL> ALTER DATABASE open resetlogs; ALTER DATABASE open Resetlo GS * ERROR at line 1:ora-00392:log 3 of thread 1 are being cleared, operation not allowed Ora-00312:online log 3 thread 1: '/oradata/sincnet/redo03.log '--View fault description information sql> ho oerr ora 00392 00392, 00000, "Log%s of thread%s is being cleared , operation not allowed '//*cause:an operation encountered this online log in the middle of being//cleared.
The command that began the clearing may have terminated//without completing the clearing. *action:if the clear command is still executing then a wait for its//completion.

If It terminated then reissue the clear command, or//drop the log. --The following SQL statement table name 3 log files are in clearing state sql> Select Group#,bytes/1024/1024| | '

M ', status from V$log; group# bytes/1024/1024| | ' M ' STATUS-------------------------------------------------------------------1 50M clearing 3 50M clearing_current 2 50 M Clearing</code> 

Second, fault handling

<code class= "Hljs vhdl" ><code class= "Hljs vhdl" > Execute clear LogFile command directly below sql> ALTER DATABASE clear logfile G
Roup 1;
Database altered.
Sql> ALTER DATABASE Clear LOGFILE GROUP 2;
Database altered.
Sql> ALTER DATABASE Clear LOGFILE GROUP 3;
Database altered. --View the status again, at which point the status appears as a common few normal states sql> Select Group#,bytes/1024/1024| | '
M ', status from V$log; group# bytes/1024/1024| | ' M ' STATUS-------------------------------------------------------------------1 50M unused 3 50M current 2 50M unused--
Try open Resetlog again, still wrong, instance terminate, need upgrade sql> ALTER DATABASE open resetlogs; ALTER DATABASE open Resetlogs * ERROR at line 1:ora-01092:oracle instance terminated. Disconnection forced Ora-00704:bootstrap process failure Ora-39700:database must is opened with UPGRADE option process I d:30553 session id:1217 Serial Number:3--see if there is a Pmon process sql> ho ps-ef|grep pmon oracle 30589 30440 0 16:02 pts/1 00: 00:00/bin/bash-c ps-ef|grep Pmon Oracle 30591 30589 0 16:02 pts/1 00:00:00 grEP Pmon--author:leshami--blog:http://blog.csdn.net/leshami--try upgrade below,
Because the current backup based on a 11.2.0.1 is restored to 11.2.0.4, upgrade sql> startup upgrade is required; Ora-24324:service Handle not initialized ora-01041:internal error. Hostdef extension doesn ' t exist sql> sql> exit disconnected from Oracle Database 11g Enterprise Edition release 11. 2.0.4.0-64bit Production with the partitioning, OLAP, Data Mining and real application testing options [oracle@10134569 dbsrv]$ sqlplus/as sysdba sql*plus:release 11.2.0.4.0 Production on Wed Feb to 16:03:15 Copyright (c) 1982, 2013, Oracle.
All rights reserved.
Connected to a idle instance.
Sql> startup upgrade;
ORACLE instance started. Total System Global area 1068937216 bytes Fixed Size 2260088 bytes Variable Size 704643976 bytes Database buffers 35232153
6 bytes Redo buffers 9711616 bytes Database mounted.
Database opened. sql> @ $ORACLE _home/rdbms/admin/catupgrd.sql; --Perform upgrade scripts </code></code>

About the ora-00392ora-00312 log is clearing the fault of the tutorial small series to introduce so many people, I hope to help you!