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
Rollback to Undo in a RAC env.

Rollback to Undo in a RAC env.

2004-08-13       - By Daniel W. Fink
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

Interesting question. The docs don 't seem to address this particular
question. According to the RAC parameter section, UNDO_MANAGEMENT is not
required to be identical amongst all instances. Since each instance must
have their own undo segments (in AUM the undo tablespace), I would
theorize that it is possible to have the instances running in separate
modes. I would be concerned about 2 things (at least). First, how will
the auto undo instance perform read consistency with entries from a
manual rollback segment (of course, I 've never tested cr in a RAC
environment)? Second, what are the recovery implications?

In terms of known problems, avoid automatic undo in a high transaction
volume OLTP system. The basic process of UNDO generation and application
has not really changed, so you should not see performance problems. In
all the testing I have done or been exposed to, performance was never an
issue that could be tied to one type of undo management versus the other.

Regards,
Daniel

GUPTA, DEEPENDER wrote:

>Hi All,
>
>I am planning to covert the undo management from MANUAL to AUTO in a RAC
>environment with 2 nodes.
>
>My question is, do I need to shutdown both the instances for doing this or
>can I change this parameter for 1 instance at a time. Can oracle mount 2
>different instances with different UNDO management at a given point of time?
>
>Last time when I upgraded the compatible parameter to 9200 I tried it one by
>one first and I got the error message ORA-1105 (See ORA-1105.ora-code.com) as one instance was mounted
>with compatible parameter 817 and I was trying to mount the other one with
>compatible parameter 9200.
>
>Also pls advise if any type of performance problems has been observed with
>AUM.
>
>Regards
>
>

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --