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: RMAN, v$session_longops and Ora-03113

Tim Onions

2005-05-19

Replies:
Sorry Tim - I made the mistake of assuming it was common knowledge of how
closely linked RMAN and long ops are:( See my reply to Jared's post for more
precise details but there is no "tenuous association" between the 2 but a
100% reproducable one! It is not RMAN that causes the error (again apologies
if my original post was unclear on that point) but RMAN that suffers once
the of querying v$session_longops results in the ora-03113 error. When you
can no longer query v$session_longops without getting the error RMAN cannot
complete etc.

Hope I've done a better job in explaining myself this time.

T?

>RMAN posts to V$SESSION_LONGOPS extensively, presumably (but not
>positively)
>using the DBMS_APPLICATION_INFO packaged procedures as anybody can...

>That's the only way the two can be linked. Still unsure about how posting
>to V$SESSION_LONGOPS by RMAN can cause ORA-03113 on subsequent queries by
>other sessions -- as Jared indicates, it sounds rather tenuous to associate
>one to the other. It smacks of the logic that runs "Whatever changed
>recently must be the cause ... somehow or other"...

_________________________________________________________________
Be the first to hear what's new at MSN - sign up to our free newsletters!
http://www.msn.co.uk/newsletters

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