Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: URGENT : Corrupt logfile, unable to open database
Ingo Etienne wrote:
> Because of a corrupt logfile the database is unable to open, although it
> can be mounted...
>
> -----------------------------------------------------------------
> SVRMGR> startup;
> ORACLE instance started.
> Total System Global Area 11705004 bytes
> Fixed Size 47788 bytes
> Variable Size 11173888 bytes
> Database Buffers 409600 bytes
> Redo Buffers 73728 bytes
> Database mounted.
> ORA-00356: inconsistent lengths in change description
> ORA-00353: log corruption near block 1620 change 7791837184 time
> 01/08/99 15:53:02
> ORA-00312: online log 4 thread 1: 'C:\ORANT\DATABASE\LOG1ORCL.ORA'
> SVRMGR>
> -----------------------------------------------------------------
If you have a muliplexed online redo log files, just copy the same file from the second groop.
From Oracle Backup and Recovery:
"...Oracle provides the capability to multiplex an instance's online redo
log files to safeguard against
damage to its online redo log files. With multiplexed online redo log files,
LGWR concurrently writes
the same redo log information to multiple identical online redo log files,
thereby eliminating a single
point of online redo log failure. ..."
If not, perform an incomplete recovery up to the SCN = 7791837184:
ORA-00356: inconsistent lengths in change description
Cause: A change record in the redo log file contains lengths that do not add
up to a consistent value.
The redo log file is corrupted in some way.
Action: Perform recovery with a good version of the redo log file or perform
time-based recovery up
to the indicated time.
ORA-00353: log corruption near block num change str time str
Cause: Some type of redo log file corruption has been discovered. This
message describes the
location of the corruption. Other messages will accompany this message and
describe the type of
corruption.
Action: Perform recovery with a good version of the redo log file or perform
incomplete recovery up to
the indicated change or time. For more information about recovery and
incomplete recovery, see the
index entries on "recovery, incomplete" and on "redo log files" in Oracle8
Server Concepts.
Sincerely.
S.P.Pohilko
Received on Wed Jan 13 1999 - 18:43:26 CST
![]() |
![]() |