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-12       - By Hameed, Amir

Reply:     1     2     3     4  

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 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7233.28">
<TITLE>Question on RAC user-managed recovery</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=2 FACE="Comic Sans MS">Folks,</FONT>

<BR><FONT SIZE=2 FACE="Comic Sans MS">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 SIZE=2 FACE=
"Comic Sans MS">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 SIZE=2 FACE="Comic Sans MS">Thank you</FONT>

<BR><FONT SIZE=2 FACE="Comic Sans MS">Amir</FONT>
</P>

<P><FONT SIZE=2 FACE="Courier New">SQL&gt; recover database until time '2006-01
-12:15:20:00' using backup controlfile</FONT>

<BR><FONT SIZE=2 FACE="Courier New">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 SIZE=2 FACE="Courier New">ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u107/oradata
/archives/e52rac/log_1_778.dbf</FONT>

<BR><FONT SIZE=2 FACE="Courier New">ORA-00280 (See ORA-00280.ora-code.com): change 7286467501233 for thread
1 is in sequence #778</FONT>
</P>

<P><FONT SIZE=2 FACE="Courier New">Specify log: {&lt;RET&gt;=suggested |
filename | AUTO | CANCEL}</FONT>
</P>
<BR>

<P><FONT SIZE=2 FACE="Courier New">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 SIZE=2 FACE="Courier New">ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u107/oradata
/archives/e52rac/log_2_463.dbf</FONT>

<BR><FONT SIZE=2 FACE="Courier New">ORA-00280 (See ORA-00280.ora-code.com): change 7286467501233 for thread
2 is in sequence #463</FONT>
</P>

<P><FONT SIZE=2 FACE="Courier New">Specify log: {&lt;RET&gt;=suggested |
filename | AUTO | CANCEL}</FONT>
</P>
<BR>

<P><FONT SIZE=2 FACE="Courier New">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 SIZE=2 FACE="Courier New">ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u107/oradata
/archives/e52rac/log_3_408.dbf</FONT>

<BR><FONT SIZE=2 FACE="Courier New">ORA-00280 (See ORA-00280.ora-code.com): change 7286467501233 for thread
3 is in sequence #408</FONT>
</P>

<P><FONT SIZE=2 FACE="Courier New">Specify log: {&lt;RET&gt;=suggested |
filename | AUTO | CANCEL}</FONT>
</P>
<BR>

<P><FONT SIZE=2 FACE="Courier New">Specify log: {&lt;RET&gt;=suggested |
filename | AUTO | CANCEL}</FONT>
</P>

<P><FONT SIZE=2 FACE="Courier New">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 SIZE=2 FACE="Courier New">ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u107/oradata
/archives/e52rac/log_2_464.dbf</FONT>

<BR><FONT SIZE=2 FACE="Courier New">ORA-00280 (See ORA-00280.ora-code.com): change 7286467508134 for thread
2 is in sequence #464</FONT>

<BR><FONT SIZE=2 FACE="Courier New">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 SIZE=2 FACE="Comic Sans MS">..</FONT>

<BR><FONT SIZE=2 FACE="Comic Sans MS">..</FONT>
</P>

</BODY>
</HTML>