Re: Interesting RMAN duplicate problem.

  • From: Marcin Przepiorowski <pioro1@xxxxxxxxx>
  • To: norman.dunbar@xxxxxxxxxxxxxxxxxxxxxxxxx
  • Date: Wed, 27 Jan 2010 15:30:15 +0000

On Wed, Jan 27, 2010 at 2:12 PM, Dunbar, Norman
<norman.dunbar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Hi Pete,
>
>>> If you try the "recover database until cancel" command in
>>> sql*plus, what does it ask for?
> A missing log file that I do not have - sequence 675041. This is higher
> than the range of sequences in the archivelog backup - 674565 - 674627.

Hi,

Did you apply all these archive log between 674565 - 674627 ?
Check alert log if all of those had been applied without errors.

If restore process is asking about higher sequence there is a chance
that control file is a newer than data files.

Did you try with recreation of control file ?

1. backup current control file to trace
2. shutdown db
3. copy current control file - just in case
4. startup nomount
5. use trace file to recreate control file with resetlog option

Duplication process without until time restriction is trying to
restore DB to current production state
and if I remember correctly there was some issues related to that in
9i - but most of them could be solved via control file recreation.

regards,
Marcin
--
//www.freelists.org/webpage/oracle-l

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 01-2010