> Specify log: {<RET>=suggested | filename
| AUTO | CANCEL}
> cancel
> 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/oracle/PNYTP102/u01/system_01.dbf'
MetaLink Note:290985.1
Incomplete RMAN Recovery gives error ORA-01547
Symptoms
RMAN recovery with an 'until'
clause giving errors:
RMAN-11001: Oracle Error: ORA-01547: warning:
RECOVER succeeded but OPEN
RESETLOGS would get error below
ORA-01152: file
... was not restored from a sufficiently old backup
ORA-01110: data file
............
Cause
In order for the database to open after
recovery, the datafiles must be consistent. If incomplete
recovery is
performed, the recovery must be (at least) enough to make the files consistent.
With
online backups, because the files are changing as the backup occurs,
recovery must apply all archives generated between the beginning through the end
of the backup.
The main error is the ORA-01152. This occurs because one
file is ahead of the others at the requested recovery stop
time.
Fix
To implement the solution, please execute the following
steps:
1. Reexecute script using a longer recovery with the 'set until'
clause.
If using 'SET UNTIL LOGSEQ' consider the definition of 'set until
logseq' from Oracle9i Recovery Manager Reference, untilclause:
"Specifies
a redo log sequence number and thread as an upper limit. RMAN selects only files
that can be used to recover up to but not including the specified sequence
number. For example, REPORT OBSOLETE UNTIL SEQUENCE 8000 THREAD 1 reports only
backups that could be used to recover through log sequence
7999."
In short, be sure the LOGSEQ
specified is one greater than the last one created after the database backup
completes.
Regards
Dimitre
