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 Gorman


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"...

on 5/18/05 10:35 AM, Jared Still at jkstill@(protected):

> Hi Tim,
> I am confused about the connection between v$session_longops and
> making a backup.
> Your email asserts that the v$session_longops problem prevents
> backups, but I don't see the connection.
> Jared
> On 5/16/05, Tim Onions <att755@(protected):
>> under Windows 2000 sp4 using Veritas Netbackup (Apologies if
>> this
>> did get posted already but I received a failure notification so I assumed
>> it
>> had not.)
>> Dear All
>> We are seeing far more regular issues with v$session_longops causing a
>> ORA-03113 when you try and select from it since we upgraded to the
>> terminal
>> release of 8.1.7 and at roughly the same time moved from Tivoli to Veritas
>> for our RMAN backup back-end.
>> Metalink says fixed in 9.2 which we will go to in due course but not for a
>> few more months (I know we should be there already but....). Other than
>> that
>> it says you have to bounce your DB which we can only do at weekends - so
>> if
>> the problem occurs on a Monday we are without backups all week.
>> I would like to know if anybody has any knowledge of what causes
>> v$session_longops to go "bad" (so I can avoid it), or how to work around
>> it
>> when it is bad (Metalink says try setting hash_joins_enable FALSE but that
>> does not work for me). I see one backport request for a fix in Metalink
>> but
>> nothing to say it ever got done or if so for my platform (probably not as
>> I
>> rasied a TAR and they denied any existance of a backport) - so any
>> knowledge
>> of a backport would be appreciated too.
>> Many thanks
>> Tim Onions - Oracle DBA
>> _________________________________________________________________
>> Winks & nudges are here - download MSN Messenger 7.0 today!
>> http://messenger.msn.co.uk
>> --
>> http://www.freelists.org/webpage/oracle-l