Database Backup and Recovery (MOSC)

MOSC Banner

Cannot copy database to new server after redo log corruption

edited Dec 3, 2009 4:07AM in Database Backup and Recovery (MOSC) 9 commentsAnswered
I had a redo log corruption last November (yes, a year ago) and I thought I had recovered from that.  I created all new redo log groups and files, switched, resetlogs and everything, but now I'm trying to move my production db to a new server and keep getting an error that the System01.dbf file needs further recovery.  The archive log thread it is looking for is from over a year ago, I purged all the old archive logs about 9 months ago and can't get the system file recovered.

A couple of questions: Is there a way to tell in the up-and-running production database that there is a problem with the system datafile?  And if there is a problem, can I fix it in the production database so I can back it up?  And can I get the redo log reset so I can start my RMAN backups (just started them about 3 weeks ago) to restore to the new server with no errors?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center