Re: Interesting RMAN duplicate problem.
From: Marcin Przepiorowski <pioro1_at_gmail.com>
Date: Wed, 27 Jan 2010 15:30:15 +0000
Message-ID: <3f5690af1001270730w7de36effve37e3154759cd2f0_at_mail.gmail.com>
On Wed, Jan 27, 2010 at 2:12 PM, Dunbar, Norman <norman.dunbar_at_environment-agency.gov.uk> 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.
Date: Wed, 27 Jan 2010 15:30:15 +0000
Message-ID: <3f5690af1001270730w7de36effve37e3154759cd2f0_at_mail.gmail.com>
On Wed, Jan 27, 2010 at 2:12 PM, Dunbar, Norman <norman.dunbar_at_environment-agency.gov.uk> 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 ?
- backup current control file to trace
- shutdown db
- copy current control file - just in case
- startup nomount
- 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
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Jan 27 2010 - 09:30:15 CST