Hi,
I just reproduced this on Win2000 Oracle 9.2.0.5...with a newly created test db and a minute number of archive logs. I followed the doc step for step, just like Brain did, and saw the same problem.
The only difference being that after the error I was able to open the db through the same RMAN session that errored on the 'recover' with 'alter database open RESETLOGS', and it's happily running now.......or is it?
So, was the RMAN-06025 in my case information only, and can anyone out there answer why it looks for arc logs it doesn't need, throws an error, then let's me open the db with resetlogs from the same session (or any session)?
These are the steps from the RMAN guide that were used:
To recover the database with a backup control file and a recovery catalog:
1. After connecting to the target database and recovery catalog database, start the instance without mounting the database:
STARTUP NOMOUNT
2. Restore the backup control file, then restore and recover the database. Do the following:
a. Run the RESTORE CONTROLFILE command to restore the control file to all default locations specified in the CONTROL_FILES initialization parameter. To restore a control file from an older backup, you can run SET UNTIL or specify the UNTIL clause on the RESTORE CONTROLFILE command.
b. Mount the database using the restored control file.
c. Optionally, run a SET UNTIL command for incomplete recovery. Note that you can also specify the UNTIL clause on the RESTORE and RECOVER commands.
d. Restore and recover the database as described in "Performing Basic RMAN Media Recovery".
This example restores the control file to its default location, then restores and completely recovers the database:
RESTORE CONTROLFILE;
ALTER DATABASE MOUNT;
RESTORE DATABASE;
RECOVER DATABASE; *THIS IS WHERE THE RMAN-06025 came up
3. If recovery was successful (WHICH IT REALLY WASN'T), then open the database and reset the online logs:
ALTER DATABASE OPEN RESETLOGS;
-----Original Message-----
From: brian
[mailto:oracledba-ezmlmshield-x79394452.[Email address protected]
Sent: Tuesday, December 28, 2004 11:51 PM
To: LazyDBA Discussion
Subject: RMAN recover error 06025
Hello.
We are oracle 9.2.0.4 AIX 5.2
I am testing out using RMAN. I AM using a recovery catalog. I am in
archivelog mode.
The test is:
1) Backup using rman, plus archivelog.
2) shutdown
3) delete the datafiles, but leave control files, online redos and archived
logs intact.
4) startup mount
5) restore database - works OK.
6) recover database gives me the error:
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 126 scn 993426 found to restore
I have checked the list backups and that log file is on the backups. There
are many archivelogs, both before sequence 126 and after. The change in
sequence 126 was applied to the database last week. That file is on disk,
owned by oracle with the proper permissions. The RECOVER should not even
need that at all!
I have tried doing another backup archivelog all, resyncing the catalog,
crosscheck archivelog , and these all check out OK.
But the recover command still gives me that error!
The kicker is, I then go into SQLPLUS as sysdba, issue a recover database,
it replays all archive logs (it doesn't even look for sequence 126 because
that was in the database well before the backup). It finishes fine, and I
can issue alter database open; and all is well.
Does anyone have any RMAN insight on this?
THANK YOU!
<<<<<>>>>>
Brian
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these terms:http://www.lazydba.com/legal.html
Oracle LazyDBA home page