You get these messages if you originally start with "recover database" command and later switch to "recover database until cancel".
Check the V$datafile view and make sure all the datafiles are at the same change number. If you find that all have the same change no, then recreate the controlfile and open the database with resetlogs.
I too faced the same problem yesterday.And i executed the same steps as u did.Just the same steps.But like u i too didn't succeeded
Then in my backup control file i placed the NORESETLOGS Option in create controlfile command and i ran this controlfile.Because, if u put noresetlogs it will make ur control file current.and you can open your database simply like that.If you solved this problem by now it's cool.If not,and still you end up with any problems reg. this let me know.
How have you perform your restore/recovery? Are you sure you restored all the files from the same backup? Have you also restored your controlfile from your backup (not very good idea if you have usable current controlfile, but must be done under certain circumstances...)? It seems to me that (at least) your system01.dbf datafile is from a backup taken later than your backup controlfile or smth simmilar... Please provide all of your steps when performing restore and recover.
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
The best thing that I can recommend is that you spend a few days doing all kinds of restores on a test machine. I learned an awful lot and destroyed the database 6-8 times before I started to see the logic of the whole thing. The resetlogs can be a bit dangerous because it starts a new era of the db.
I would never "learn" how to restore on a live production db. Once you F***ed up it may be hard to come back without a cold backup from before you started playing with the restores.