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



RMAN uses v$session_longops to record it's progress. After each backup set
it uses the DBMS package to update "progress" in the V$ view, having first
queried out of the view to find some relevant data within . So when the view
goes "bad" RMAN does its initial backup set/piece, trys to update
v$session_longops and subsequently gets an Ora-03113 error and dies. Hence,
the backup "fails" inasmuch as it did not run to completion. I reality we
get less than 10% of our Db backed-up when this problem is in force.

The query RMAN runs (and gets ora-03113 from) is:

select sofar, context from v$session_longops where sid = (select distinct
sid from v$mystat) and opname like 'RMAN:%' order by start_time desc,
context desc

Hope this is clear


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

Winks & nudges are here - download MSN Messenger 7.0 today!