Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
Question on RAC user-managed recovery

Question on RAC user-managed recovery

2006-01-19       - By Tanel Poder

Reply:     1     2     3     4  

Question on RAC user-managed recoveryHi,

The recovery start SCN is common in the first lines because recovery has to
read redo from the smallest checkpoint SCN found in controlfile checkpoint
progress records (or datafile headers if recovering using backup controlfile
option).

And this information is database specific, global to all RAC instances
servicing your database, thus all redo threads have to be scanned from the same
SCN.

Tanel.

 -- -- Original Message -- --
 From: Hameed, Amir
 To: ORACLE-L ; racdba@(protected)
 Sent: Thursday, January 12, 2006 4:37 PM
 Subject: Question on RAC user-managed recovery


 Folks,
 I am running some time-based database instance recovery tests in the lab on a
three-node RAC environment. The following command was issued from one RAC
instance while the others were down. I am trying to understand the way the
change number (change 7286467501233) is being displayed on the first line of
each of the first three threads below. Why is this number common here? After
that, this number is distinct in each subsequent archived log file. I would
appreciate if someone can explain/clarify it for me.

 Thank you
 Amir

 SQL> recover database until time '2006-01-12:15:20:00' using backup
controlfile
 ORA-00279 (See ORA-00279.ora-code.com): change 7286467501233 generated at 01/11/2006 14:38:59 needed for
thread 1
 ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u107/oradata/archives/e52rac/log_1_778.dbf
 ORA-00280 (See ORA-00280.ora-code.com): change 7286467501233 for thread 1 is in sequence #778

 Specify log: {<RET>=suggested | filename | AUTO | CANCEL}



 ORA-00279 (See ORA-00279.ora-code.com): change 7286467501233 generated at 01/11/2006 14:38:35 needed for
thread 2
 ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u107/oradata/archives/e52rac/log_2_463.dbf
 ORA-00280 (See ORA-00280.ora-code.com): change 7286467501233 for thread 2 is in sequence #463

 Specify log: {<RET>=suggested | filename | AUTO | CANCEL}



 ORA-00279 (See ORA-00279.ora-code.com): change 7286467501233 generated at 01/11/2006 14:38:37 needed for
thread 3
 ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u107/oradata/archives/e52rac/log_3_408.dbf
 ORA-00280 (See ORA-00280.ora-code.com): change 7286467501233 for thread 3 is in sequence #408

 Specify log: {<RET>=suggested | filename | AUTO | CANCEL}



 Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

 ORA-00279 (See ORA-00279.ora-code.com): change 7286467508134 generated at 01/11/2006 14:43:27 needed for
thread 2
 ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u107/oradata/archives/e52rac/log_2_464.dbf
 ORA-00280 (See ORA-00280.ora-code.com): change 7286467508134 for thread 2 is in sequence #464
 ORA-00278 (See ORA-00278.ora-code.com): log file '/u107/oradata/archives/e52rac/log_2_463.dbf' no longer
needed for this recovery
 ..
 ..

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Question on RAC user-managed recovery</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>The recovery start SCN is common in the first
lines
because recovery has to read redo from the smallest checkpoint SCN found in
controlfile checkpoint progress records (or datafile headers if recovering
using
backup controlfile option).</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>And this information is database specific, global
to all RAC instances servicing your database, thus all redo threads have to be
scanned from the same SCN.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Tanel.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT:
#000000 2px solid; MARGIN-RIGHT: 0px">
 <DIV style="FONT: 10pt arial">-- -- Original Message -- -- </DIV>
 <DIV
 style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
 <A title=Amir.Hameed@(protected) href="mailto:Amir.Hameed@(protected)">Hameed,
 Amir</A> </DIV>
 <DIV style="FONT: 10pt arial"><B>To:</B> <A title=oracle-l@(protected)
 href="mailto:oracle-l@(protected)">ORACLE-L</A> ; <A
 title=racdba@(protected)
 href="mailto:racdba@(protected)">racdba@(protected)</A> </DIV>
 <DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, January 12, 2006 4:37
 PM</DIV>
 <DIV style="FONT: 10pt arial"><B>Subject:</B> Question on RAC user-managed
 recovery</DIV>
 <DIV><FONT face=Arial size=2></FONT><FONT face=Arial size=2></FONT><BR></DIV>
<!-- Converted from text/rtf format -->
 <P><FONT face="Comic Sans MS" size=2>Folks,</FONT> <BR><FONT
 face="Comic Sans MS" size=2>I am running some time-based database instance
 recovery tests in the lab on a three-node RAC environment. The following
 command was issued from one RAC instance while the others were down. I am
 trying to understand the way the change number (</FONT><FONT
 face="Comic Sans MS" size=2>change 7286467501233) is being displayed on the
 first line of each of the first three threads below. Why is this number
common
 here? After that, this number is distinct in each subsequent archived log
 file. I would appreciate if someone can explain/clarify it for me.</FONT></P>
 <P><FONT face="Comic Sans MS" size=2>Thank you</FONT> <BR><FONT
 face="Comic Sans MS" size=2>Amir</FONT> </P>
 <P><FONT face="Courier New" size=2>SQL&gt; recover database until time
 '2006-01-12:15:20:00' using backup controlfile</FONT> <BR><FONT
 face="Courier New" size=2>ORA-00279 (See ORA-00279.ora-code.com): change 7286467501233 generated at
 01/11/2006 14:38:59 needed for thread 1</FONT> <BR><FONT face="Courier New"
 size=2>ORA-00289 (See ORA-00289.ora-code.com): suggestion :
 /u107/oradata/archives/e52rac/log_1_778.dbf</FONT> <BR><FONT
 face="Courier New" size=2>ORA-00280 (See ORA-00280.ora-code.com): change 7286467501233 for thread 1 is in
 sequence #778</FONT> </P>
 <P><FONT face="Courier New" size=2>Specify log: {&lt;RET&gt;=suggested |
 filename | AUTO | CANCEL}</FONT> </P><BR>
 <P><FONT face="Courier New" size=2>ORA-00279 (See ORA-00279.ora-code.com): change 7286467501233 generated
 at 01/11/2006 14:38:35 needed for thread 2</FONT> <BR><FONT face="Courier New
"
 size=2>ORA-00289 (See ORA-00289.ora-code.com): suggestion :
 /u107/oradata/archives/e52rac/log_2_463.dbf</FONT> <BR><FONT
 face="Courier New" size=2>ORA-00280 (See ORA-00280.ora-code.com): change 7286467501233 for thread 2 is in
 sequence #463</FONT> </P>
 <P><FONT face="Courier New" size=2>Specify log: {&lt;RET&gt;=suggested |
 filename | AUTO | CANCEL}</FONT> </P><BR>
 <P><FONT face="Courier New" size=2>ORA-00279 (See ORA-00279.ora-code.com): change 7286467501233 generated
 at 01/11/2006 14:38:37 needed for thread 3</FONT> <BR><FONT face="Courier New
"
 size=2>ORA-00289 (See ORA-00289.ora-code.com): suggestion :
 /u107/oradata/archives/e52rac/log_3_408.dbf</FONT> <BR><FONT
 face="Courier New" size=2>ORA-00280 (See ORA-00280.ora-code.com): change 7286467501233 for thread 3 is in
 sequence #408</FONT> </P>
 <P><FONT face="Courier New" size=2>Specify log: {&lt;RET&gt;=suggested |
 filename | AUTO | CANCEL}</FONT> </P><BR>
 <P><FONT face="Courier New" size=2>Specify log: {&lt;RET&gt;=suggested |
 filename | AUTO | CANCEL}</FONT> </P>
 <P><FONT face="Courier New" size=2>ORA-00279 (See ORA-00279.ora-code.com): change 7286467508134 generated
 at 01/11/2006 14:43:27 needed for thread 2</FONT> <BR><FONT face="Courier New
"
 size=2>ORA-00289 (See ORA-00289.ora-code.com): suggestion :
 /u107/oradata/archives/e52rac/log_2_464.dbf</FONT> <BR><FONT
 face="Courier New" size=2>ORA-00280 (See ORA-00280.ora-code.com): change 7286467508134 for thread 2 is in
 sequence #464</FONT> <BR><FONT face="Courier New" size=2>ORA-00278 (See ORA-00278.ora-code.com): log file
 '/u107/oradata/archives/e52rac/log_2_463.dbf' no longer needed for this
 recovery</FONT> <BR><FONT face="Comic Sans MS" size=2>..</FONT> <BR><FONT
 face="Comic Sans MS" size=2>..</FONT> </P></BLOCKQUOTE></BODY></HTML>