A reader, April 11, 2017 - 4:50 am UTC
when i restore database using control file i getting following error.
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 3 and starting SCN of 6945324467766 know.
And I also restore a archivelog which generate new then also not work.
how to resolve>
Recovered
Fahd, April 11, 2017 - 2:41 pm UTC
Great Connor McDonald. Database is recovered by the second solution you gave. You deserve a lot of Thanks.
I thing i want to ask that how can i backup database so that i get move control over recovery rather than RMAN doing some unpredictable stuff for me, before i get to know all the features of RMAN. I can afford to restart database or can do down for some hours. I can work more, use more space but i need predictable recovery. Solution ?
April 12, 2017 - 4:58 am UTC
If you are just playing with the database, an easy cold backup is:
- shutdown
- copy all files (datafiles/controlfile/redo/spfile/etc etc) to a location
- startup
and that can be just copied back into place whenever you need to go back to that point.
But I'd spend some time looking at RMAN - so many cool things to explore in there.
RMAN
Fahd, April 12, 2017 - 6:54 am UTC
RMAN is really a cool tool.
I am studying RMAN intensively.
Reading Oracle Doc on Backup and Recovery, but there is so much to read.
Can you point out some short but rather practical starting point to RMAN.
April 13, 2017 - 1:43 am UTC
Google for "RMAN Recipes". There are books and whitepapers out there which talk about a set of "common tasks" that you'll typically need RMAN for.
That's a nice easy way to get you started.
John
A reader, April 12, 2017 - 8:17 am UTC
when i restore database using control file i getting following error.
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 3 and starting SCN of 6945324467766 know.
And I also restore a archivelog which generate new then also not work.
how to resolve?
April 13, 2017 - 1:47 am UTC
If you used a backup controlfile, thats to be expected, because we no longer have a record of what archivelog you were up to...so we just keep going until we can no longer find them.
You should be able to do
alter database open resetlogs
at this point