Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: URGENT : Backdoor required for corrupt redo
Neil,
Hi. This is what the Revealnet says about the same.
Startup with a corrupted redo log
There may be situations where you need to startup with acorrupted redo log. In this case there is an init.ora parameter that allows this:
_ALLOW_RESETLOGS_CORRUPTED=TRUE
However, this will startup even if it results in corrupteddata, so only use it if you have to and only to startup long enough to get an export of critical data. Use only under the guidance of Oracle Support.
This however works only with corrupted redo logs. You seem to have LOST your
redo logs.
I would say that you should perform a cancel based recovery till you reach a log
which you have.
Tapan
Neil Cudd wrote:
> Hi all,
>
> I know the backdoor for cracking a V7 database open with lost redo log files
> :
>
> _allow _redo_logs_corruption=true
>
> but can anyone tell me how to do it with a V8.0.4.3 database ? This line
> does not seem to work.
>
> Would help me immensely if anyone can answer.
> Thanks,
>
> Neil C.
Received on Mon Dec 13 1999 - 14:00:16 CST
![]() |
![]() |