If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

The original log file is REDO03.LOG. I thought renaming to REDO033.LOG might help, then afterwards when I executed 'startup mount;' command, the database got mounted successfully. But on trying 'alter database open resetlogs;' I started receiving below error:

Calling oracle support is the last option for all the DBAs on the earth after putting every attempt from there side. Thanks for your suggestion.

As per the error posted, I understood that one of the redo logs had a block corruption. He didn't mention whether that redo log is current or inactive. He renamed the corrupted log with other name (not sure how far renaming on the same physical location works). So, the work around i suggest is ...

1. Recover until cancel
2. Open resetlogs.

Appreciate comments on this.

Thanks,

Vijay Tummala

Try hard to get what you like OR you will be forced to like what you get.

Calling oracle support is the last option for all the DBAs on the earth after putting every attempt from there side. Thanks for your suggestion.

WHAT? if you have no clue - oracle support is the first call, thats what you pay them for!

As per the error posted, I understood that one of the redo logs had a block corruption. He didn't mention whether that redo log is current or inactive. He renamed the corrupted log with other name (not sure how far renaming on the same physical location works). So, the work around i suggest is ...