Physical removal of all redo log recovery methods in the "Oracle" database running state

Lab Environment:

OEL5.6 Oracle11.2.0.1

Experiment begins:

Database run state, delete all logs:

[[email protected] test]$ ls

Control01.ctl Redo01.log sysaux01.dbf undotbs01.dbf

DATA_OL01.DBF Redo02.log system01.dbf users01.dbf

EXAMPLE01.DBF Redo03.log temp01.dbf

[Email protected] test]$ RM-RF *.log

To switch the log group in the database:

[Email protected]>alter system switch logfile;

System altered.

[Email protected]>/

System altered.

[Email protected]>/

ALTER SYSTEM switch logfile

*

ERROR at line 1:

Ora-01013:user requested cancel of current operation

[Email protected]>insert into T-select * from Dba_objects;

72504 rows created.

[Email protected]>/

72504 rows created.

[Email protected]>/

72504 rows created.

[Email protected]>/

72504 rows created.

[Email protected]>/

72504 rows created.

[Email protected]>/

At this time the database hung Live, all business is suspended,alert log error as follows:

Mon Jul 13 17:03:28 2015

Errors in FILE/U01/APP/ORACLE/DIAG/RDBMS/TEST/TEST/TRACE/TEST_M000_23367.TRC:

Ora-00313:open failed for members of log Group 1 of thread 1

Ora-00312:online Log 1 Thread 1: '/u01/app/oracle/oradata/test/redo01.log '

Ora-27037:unable to obtain file status

Linux error:2: No such file or directory

Additional Information:3

Errors in FILE/U01/APP/ORACLE/DIAG/RDBMS/TEST/TEST/TRACE/TEST_M000_23367.TRC:

Ora-00313:open failed for members of log Group 2 of thread 1

Ora-00312:online Log 2 thread 1: '/u01/app/oracle/oradata/test/redo02.log '

Ora-27037:unable to obtain file status

Linux error:2: No such file or directory

Additional Information:3

Errors in FILE/U01/APP/ORACLE/DIAG/RDBMS/TEST/TEST/TRACE/TEST_M000_23367.TRC:

Ora-00313:open failed for members of log Group 3 of thread 1

Ora-00312:online Log 3 thread 1: '/u01/app/oracle/oradata/test/redo03.log '

Ora-27037:unable to obtain file status

Linux error:2: No such file or directory

Additional Information:3

Temporarily turn off monitoring to prevent the new business from fillingup the session, at which point the new connection can connect properly to the database.

Do not stop the library at this time, because the database has been unable to gracefully shut down, once the database is down, data will inevitably be lost.

At this point, using SYSDBA to connect to the database, clear The log group directly, the database can resume normal operation.

[Email protected]>alter database Clear unarchived logfile Group 1;

Database altered.

[Email protected]>alter database Clear unarchived logfile Group 2;

Database altered.

[Email protected]>alter database Clear unarchived logfile Group 3;

Database altered.

The database runs back to normal.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Physical removal of all redo log recovery methods in the "Oracle" database running state