Home
All Oracle Error Codes
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

Re: Question on RAC user-managed recovery

Jonathan Lewis

2006-01-12

Replies:

It's just part of the way that RAC works.

You have three nodes that are independent; they
re-synchronize their SCNs very frequently - but
in principle could delay re-synchronization for about
3 seconds. So if you happened to have three transactions
take place one the three separate nodes just after a
re-synch, then all three nodes would have to commit
at the same SCN.


Regards

Jonathan Lewis

http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users' FAQ

http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html
Cost Based Oracle: Fundamentals

http://www.jlcomp.demon.co.uk/appearances.html
Public Appearances - schedule updated 10th Jan 2006

----- Original Message -----
From: "Hameed, Amir" <Amir.Hameed@(protected)>
To: "ORACLE-L" <oracle-l@(protected)>
Sent: Thursday, January 12, 2006 10: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: change 7286467501233 generated at 01/11/2006 14:38:59 needed
for thread 1
ORA-00289: suggestion : /u107/oradata/archives/e52rac/log_1_778.dbf
ORA-00280: change 7286467501233 for thread 1 is in sequence #778

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


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

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


ORA-00279: change 7286467501233 generated at 01/11/2006 14:38:37 needed
for thread 3
ORA-00289: suggestion : /u107/oradata/archives/e52rac/log_3_408.dbf
ORA-00280: 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: change 7286467508134 generated at 01/11/2006 14:43:27 needed
for thread 2
ORA-00289: suggestion : /u107/oradata/archives/e52rac/log_2_464.dbf
ORA-00280: change 7286467508134 for thread 2 is in sequence #464
ORA-00278: log file '/u107/oradata/archives/e52rac/log_2_463.dbf' no
longer needed for this recovery
..
..



--
http://www.freelists.org/webpage/oracle-l