Monday, February 27, 2012

ORA-00333: redo log read error block 17258 count 7490

After a power failure, at startup we received folowing error
ORA-00333: redo log read error block 17258 count 7490

When i tried to do
alter database clear logfile '/u02/app/oracle/oradata/redo01.log',

i received
ORA-1624 signalled during: alter database clear logfile '/u02/app/oracle/oradata/redo01.log'...

The only solutions was restore of database, from a full backup with rman.
The control file was ok

RMAN> connect target /
RMAN> startup mount;
RMAN> restore database;
RMAN> alter database open resetlogs;


RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 02/27/2012 16:18:45
ORA-01139: RESETLOGS option only valid after an incomplete database recovery

from this connect to SQL Plus

SQL> recover database until cancel;
ORA-00279

SQL> cancel
SQL> alter database open resetlogs;

if the control file was not ok.

RMAN> connect target /
RMAN> startup nomount;
RMAN> restore controlfile from autobackup;
RMAN> alter database mount;
RMAN> restore database;
RMAN> alter database open resetlogs;






2 comments:

  1. SQL> conn /as sysdba;
    Connected.
    SQL> select * from emp;
    select * from emp
    *
    ERROR at line 1:
    ORA-01219: database not open: queries allowed on fixed tables/views only


    SQL> shutdown immediate
    ORA-01109: database not open


    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance started.

    Total System Global Area 535662592 bytes
    Fixed Size 1384760 bytes
    Variable Size 218107592 bytes
    Database Buffers 310378496 bytes
    Redo Buffers 5791744 bytes
    Database mounted.
    SQL> alter database open;
    alter database open
    *
    ERROR at line 1:
    ORA-00333: redo log read error block 243 count 7952

    ReplyDelete
    Replies
    1. Follow the recovery steps and open database with resetlogs.

      Delete