ORA-01122: database file 1 failed verification check

hi am having this error when starting database
SQL> startup
ORACLE instance started.

Total System Global Area 1728053248 bytes
Fixed Size                  3004520 bytes
Variable Size            1056966552 bytes
Database Buffers          654311424 bytes
Redo Buffers               13770752 bytes
Database mounted.
ORA-01122: database file 1 failed verification check
ORA-01110: data file 1:
ORA-01207: file is more recent than control file - old control file

Open in new window

the database is 12c in solaris
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

slightwv (䄆 Netminder) Commented:
This question and your last one are pretty much duplicates of everything covered in your other question:

There is nothing to post here that isn't already covered there.

The error means you have a DBF file that has a newer header than the control file.  My guess is from some improper recovery based on the question referenced above.

It looks like you copied a new DBF file from somewhere and didn't copy a newer control file to match it.
Mark GeerlingsDatabase AdministratorCommented:
Can you tell us what actually happened in your system before you started seeing these errors?  Or do you just want us to keep guessing about all of the possible things that may have happened?
johnsoneSenior Oracle DBACommented:
These messages were in the alert log that was in the post that slightwv references.  Based on my original quick scan of that log, there is no telling what happened.  Looks like control files were recreated, partial backup files put back in place, recoveries attempted, mixed versions of data files and control files, possible changed parameters (I say that based on messages about differing file sizes and block differences), offline drop of undo, a lot of different things that all seem to be leading up to most likely corrupted files.

I will reiterate what I said in the other thread.  Restore and start over.  Personally, it looks like too much damage was done experimenting and I don't think it can be undone.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.