Re: RMAN DUPLICATE failed at recovery time.

This is what is logged in the RMAN log when the duplication is
performing point in time recovery of the restored datafiles :
-----------------------------------------------------------------------------------------------
starting media recovery
RMAN-06560: WARNING: backup set with key 195101 will be read 3 times
RMAN-06560: WARNING: backup set with key 195102 will be read 3 times
RMAN-06560: WARNING: backup set with key 195103 will be read 3 times

available space of 6237788 kb needed to avoid reading the backup set
multiple times
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=18247
channel aux1: reading from backup piece /backup/arch_dtfiles/
crkf7pg0_1_1
channel aux1: restored backup piece 1
piece handle=/backup/arch_dtfiles/crkf7pg0_1_1
tag=REMAINING_ARCHIVELOG_BACKUP
channel aux1: restore complete, elapsed time: 00:04:46
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get
error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/data-lv/oradata/system01.dbf'

released channel: aux1
released channel: aux2
released channel: aux3
released channel: aux4
RMAN-00571:
===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
===========================================================
RMAN-03002: failure of Duplicate Db command at 05/19/2009 10:08:01
RMAN-03015: error occurred in stored script Memory Script
RMAN-06561: available space must be larger than 2061949 kb

Recovery Manager complete.
------------------------------------------------------------------

The backup contains three compressed backup sets (1 backup piece each)
with archived logs (TAG: REMAINING_ARCHIVELOG_BACKUP), Oracle shows a
warning specifying the backup sets Keys. What is shocking to me is
that it is trying to recover the database with the newest logs and
leaves the older ones behind, hence the recovery issue.

Executing the RMAN list command on the target DB to get information in
archived logs backed up during the full target DB backup:

--------------------------------------------------------------------------------------------------------------------
RMAN> list backup tag REMAINING_ARCHIVELOG_BACKUP;

List of Backup Sets
===================

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
195101 1.53G DISK 00:07:55 17-MAY-09
BP Key: 195108 Status: AVAILABLE Compressed: YES Tag:
REMAINING_ARCHIVELOG_BACKUP
Piece Name: /backup/djprod1/arch_dtfiles/crkf7pg0_1_1

List of Archived Logs in backup set 195101
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 18247 13753652757 17-MAY-09 13753968692 17-MAY-09
1 18248 13753968692 17-MAY-09 13754284761 17-MAY-09
1 18249 13754284761 17-MAY-09 13754519417 17-MAY-09

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
195102 1.66G DISK 00:08:58 17-MAY-09
BP Key: 195109 Status: AVAILABLE Compressed: YES Tag:
REMAINING_ARCHIVELOG_BACKUP
Piece Name: /backup/djprod1/arch_dtfiles/cpkf7pg0_1_1

List of Archived Logs in backup set 195102
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 18244 13752701081 17-MAY-09 13753019578 17-MAY-09
1 18245 13753019578 17-MAY-09 13753336611 17-MAY-09
1 18246 13753336611 17-MAY-09 13753652757 17-MAY-09

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
195103 1.71G DISK 00:09:09 17-MAY-09
BP Key: 195110 Status: AVAILABLE Compressed: YES Tag:
REMAINING_ARCHIVELOG_BACKUP
Piece Name: /backup/djprod1/arch_dtfiles/cqkf7pg0_1_1

List of Archived Logs in backup set 195103
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 18241 13751509331 16-MAY-09 13752221618 17-MAY-09
1 18242 13752221618 17-MAY-09 13752412707 17-MAY-09
1 18243 13752412707 17-MAY-09 13752701081 17-MAY-09
-----------------------------------------------------------------------------------------------

As you can see it is starting recovery from log sequence 18247, that
belongs to backup set key 195101, and is leaving behind older logs
contained in
195102 and 195103 backup sets, which explains why point in time
recovery is failing.

Is this normal?

Thanks in advance.
.

Relevant Pages

  • Re: Using backup files with new DB
    ... Do you have Oracle support? ... It would appear that you are missing the online redo logs and archived ... have to fake recovery to pull that off) which will re-create the online ... No archived logs were saved and no oracle support. ...
    (comp.databases.oracle.server)
  • Re: RMAN DUPLICATE failed at recovery time.
    ... The recovery failed because it requires more disk space. ... but is not large enough to restore files. ... 1) Increase the MAXSIZE parameter and retry the ... not delete archived logs that were already on disk before the RESTORE ...
    (comp.databases.oracle.server)
  • =?iso-8859-1?Q?Re:_Informationsspeicher_bei_Exchange_2000_h=E4ngt_beim_Be?= =?iso-8859&#
    ... > Exchange liest im laufenden Betrieb nie aus den Logs, nur beim Recovery ... Da habe ich selbst den "Microsoft Exchange ... > werden alle Logs in denen noch offene Transaktionen sind in das Fullbackup ...
    (microsoft.public.de.german.exchange2000.general)
  • Re: Recover from cold backup + archive logs question
    ... have copied the data files and control files from the cold backup into ... ORA-00264: no recovery required ... control files + old datafiles and then apply the archive logs. ... What I did discover as I applied the archive logs was that the final ...
    (comp.databases.oracle.server)
  • Re: dial tone restore and current log files.
    ... Got the logs copied into the RSG database directory. ... The restore that took 5 hours this weekend, ... Even when "Run Recovery" check box is unselected I'll receive the Pop-up ...
    (microsoft.public.exchange.admin)