My Oracle Support Banner

Recovery of restored RAC database cannot identify archivedlogs if control file is recreated (Doc ID 342784.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.3 and later
Information in this document applies to any platform.
***Checked for relevance on 30-Mar-2012***


Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used
represents fictitious data from the Oracle sample schema(s),Public Documentation delivered with an
Oracle database product or other training material. Any similarity to actual environments, actual
persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example
to describe the procedure:

 

Service Name = test90
Directory = /dbtest9000/app/oracle/admin and all subdirectories

 

Hot backup from RAC instance is restored into a single instance on a new host.


Archivedlogs from both nodes are copied to a single local directory on the new host.
Originally, the logs from both threads were written to a shared file system using identical
archive log formats.

The controlfile was then recreated because the new database is also to be renamed.
Recovery correctly identifies the first log to be applied but after that, it is unable to
identify the next log from the other thread:

SQL> recover database using backup controlfile until time '2005-11-10:08:50:00';
ORA-00279: change 809129359 generated at 11/10/2005 07:00:22 needed for thread 2
ORA-00289: suggestion :
/dbtest9000/app/oracle/admin/test90/arch/arch_2_792_550344117.arc
ORA-00280: change 809129359 for thread 2 is in sequence #792
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

The log is applied and then the next prompt is for the same SCN for thread 1 but no log is identified and specifying AUTO returns ORA-00266:


ORA-00279: change 809129359 generated at needed for thread 1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00266: name of archived log file needed

Oracle cannot identify any log apart from the first log from thread 2 which happened to be the last thread to checkpoint the data files.  If the required log name is specified explicitly (after inspecting alert log from thread 1), it is applied.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.