Hello. I was recovering a database today and had a small blip.
I issued the following:
ALTER DATABASE RECOVER database using backup controlfile
I then chose the AUTO option, allowing Oracle to select all the available logs so that it would recover up to the last log found in the archive detination
However.... the following occured:
ORA-00289: suggestion :
/u03/oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf
ORA-00280: change 30031145558 for thread 1 is in sequence #242449
ORA-00278: log file
'/u03/oracle/stk2proddata/archived_logs/arch1_242448_737547185.dbf' no longer
needed for this recovery
ORA-00308: cannot open archived log
'/u03/oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
The two messages above I expected. However, I then issued this:
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/u02/oracle/stk2proddata/system01.dbf'
This was not what I expected. What did I do wrong? Should I have, once received the "cannot open archived log" message, issued CANCEL??
I then recovered again, but used
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 30031145558 generated at 04/30/2014 09:58:34 needed for
thread 1
ORA-00289: suggestion :
/u03/oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf
ORA-00280: change 30031145558 for thread 1 is in sequence #242449
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 30031157768 generated at 04/30/2014 10:06:07 needed for
thread 1
ORA-00289: suggestion :
/u03/oracle/stk2proddata/archived_logs/arch1_242450_737547185.dbf
ORA-00280: change 30031157768 for thread 1 is in sequence #242450
ORA-00278: log file
'/u03/oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> alter database open resetlogs;
Database altered.
No problem there then. Could somebody please explain what I did wrong the first time, and right the second time? Is it an issue with AUTO and using CANCEL??
Thanks!
DA
11.2.0.2
RHEL 5.5