Quantcast
Channel: Remote Database Admin Blog » Database Administration
Viewing all articles
Browse latest Browse all 32

ORA-00354: corrupt redo log block header

$
0
0

ORA-00354: corrupt redo log block header

Issue :
Normal users could not connect to database.
It messaged ORA-00257 :Connect Internal Only until freed.
Whenever you try to archive the redo log it returns the message.

ORA-16038: log %s sequence# %s cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log %s thread %s: ‘%s’

Cause:

At alert log you will see the ORA-16038,ORA-00354,ORA-00312 error serial.
The error produced as because it failed to archive online redolog due to a corruption in the online redo file.

Solution of The problem:

Making your database running by clear the unarchived redo log.
SQL>select * from v$log;
This will show you some log is not Archived. It may be the corrupted redo log. We should clear it by unarchive it.

SQL>alter database clear unarchived logfile ‘logilename’;

This makes the corruption disappear which causes the contents of the cleared online redo file.

Try to switch the log and confirm it is working fine.

If not then you may have to recreate a redo log for that group only.

Make a complete backup of the database.


Viewing all articles
Browse latest Browse all 32

Latest Images

Trending Articles



Latest Images