RMAN Recovery

I am trying to do a test recovery on my Dev database server. I got this error: RMAN-06025: no backup of log thread 1 seq 1108 lowscn 61380386 found to restore. How do I solve this problem? The log is not there and I have no other backup file to use.

The reason for this test recovery is because I am planning to do a duplicate database from Dev to Prod server but it also fails due to it cannot find the same log.


RMAN> recover database;

Starting recover at 21-FEB-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=212 devtype=DISK

starting media recovery

archive log thread 1 sequence 1109 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01109_0738606773.001
archive log thread 1 sequence 1110 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01110_0738606773.001
archive log thread 1 sequence 1111 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01111_0738606773.001
archive log thread 1 sequence 1112 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01112_0738606773.001
archive log thread 1 sequence 1113 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01113_0738606773.001
archive log thread 1 sequence 1114 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01114_0738606773.001
archive log thread 1 sequence 1115 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01115_0738606773.001
archive log thread 1 sequence 1116 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01116_0738606773.001
archive log thread 1 sequence 1117 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01117_0738606773.001
archive log thread 1 sequence 1118 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01118_0738606773.001
archive log thread 1 sequence 1119 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01119_0738606773.001
archive log thread 1 sequence 1120 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01120_0738606773.001
archive log thread 1 sequence 1121 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01121_0738606773.001
archive log thread 1 sequence 1122 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01122_0738606773.001
archive log thread 1 sequence 1123 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01123_0738606773.001
archive log thread 1 sequence 1124 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01124_0738606773.001
archive log thread 1 sequence 1125 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01125_0738606773.001
archive log thread 1 sequence 1126 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01126_0738606773.001
archive log thread 1 sequence 1127 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01127_0738606773.001
archive log thread 1 sequence 1128 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01128_0738606773.001
archive log thread 1 sequence 1129 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01129_0738606773.001
archive log thread 1 sequence 1130 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01130_0738606773.001
archive log thread 1 sequence 1131 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01131_0738606773.001
archive log thread 1 sequence 1132 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01132_0738606773.001
archive log thread 1 sequence 1133 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01133_0738606773.001
archive log thread 1 sequence 1134 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01134_0738606773.001
archive log thread 1 sequence 1135 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01135_0738606773.001
archive log thread 1 sequence 1136 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01136_0738606773.001
archive log thread 1 sequence 1137 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01137_0738606773.001
archive log thread 1 sequence 1138 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01138_0738606773.001
archive log thread 1 sequence 1139 is already on disk as file D:\ORACLE\PRODUCT\10.2.0\DB_2\RDBMS\AR
C01139_0738606773.001
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/21/2011 11:38:17
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 1108 lowscn 61380386 found to restore

LVL 23
OP_ZaharinAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
MrNedConnect With a Mentor Commented:
There are many ways to do this and you should come up with a process to suit your requirements (do you have many databases, what availability do you need to maintain, are you backing up to disk and/or tape, how many copies do you need, are you using incremental backups, using RAC/ASM etc). Here is just one minimal example which should get the job done.

Backup Database

run {
   backup as compressed backupset database
   format 'backupdir/rman_%d_%s%p%c_df_%f_%T';
}
sql 'alter system archive log current';
backup as compressed backupset archivelog all delete all input format 'backupdir/rman_%d_%s%p%c_arch_%h_%e_%T';


Duplicate Database

rman target sys/${SYSPASS}@${SOURCE_INST} auxiliary /
duplicate target database to NEW_DB_NAME;


These were pulled from a script I wrote so might have some superfluous keywords, but I just left them in there and it should still work. Hope it makes sense.
0
 
MrNedCommented:
Did that log ever exist? Did you turn on archiving before or after that log?

Check:
select * from v$log_history
select * from v$archived_log
0
 
OP_ZaharinAuthor Commented:
hi Mr.Ned,
archiving is turn on before that log.

-from v$log_history its there
-from v$archived_log seq from 216 to 1108 the Name column is null (the physical file not exist)
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
MrNedCommented:
Sounds like it has been backed up and cleared (or simply deleted!). Is RMAN using a recovery catalog or the control file? Are there any other RMAN backups lying around that might include the missing archive log?
0
 
OP_ZaharinAuthor Commented:
It might be deleted as I can't find it anywhere.
RMAN is using control file as I didn't specify any catalog.

Any way of telling RMAN not to read from the missing log in order for me to do a fresh Backup and Duplicate to other server?

0
 
MrNedCommented:
You can definitely take a new backup without requiring previous archive logs, it should not be looking for them. Best is to take a full database backup (or level 0 incremental) as well as log files so they are kept together. I'd also suggest using a recovery catalog so old backup files are not lost (the control file only keeps records of backed up files a fixed period of time), and if you need to rebuild the control file for some reason, the backup data is still available.
0
 
OP_ZaharinAuthor Commented:
MrNed,
Can you assist me a step by step command to execute your suggestion?
0
 
OP_ZaharinAuthor Commented:
thank you MrNed. will run this..
0
 
OP_ZaharinAuthor Commented:
by the way, by executing the above backup database, it wont take the missing log?
I have done a RMAN> backup database; without taking the archivelog but when doing duplicate its still look for that missing log.
0
 
MrNedCommented:
Wait one - are you are running the backup via the web GUI? I never use that, but I believe it defaults to incremental backups so you are probably only taking a level 1 which means a duplicate still needs the previous level 0 and all logs for those two backups. You need to do a new DATABASE or LEVEL 0 backup instead.
0
 
OP_ZaharinAuthor Commented:
no i'm running it via command line.
thank you for your help mrNed :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.