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: A tale of data dictionary corruption in Oracle10gR2

John Kanagaraj

2006-10-06

Replies:
Hamid,
 
You might want to check that the timestamps for dependency$ and obj$ match. If you had aborted compilation on an APPS database, I believe this mismatch has been known to occur. If it did occur, you will get all sorts of strange ORA-600 errors. You should use the query below to determine this list and "fix" the dependency$.timestamp column manually.
 
SELECT DISTINCT NAME , o.owner#
FROM obj$ o, dependency$ d
WHERE o.stime <> d.p_timestamp
AND o.ctime <= d.p_timestamp
AND o.obj# = d.p_obj#
 
I speak from the experience of helping a colleague recover from such a disaster. We had Oracle support's blessings as it was a P1 TAR. The fix was to run the following:
 
update dependency$
set p_timestamp = (select stime from obj$ o where o.obj# =
dependency$.p_obj#)
where d_obj# = <Objid, one by one for the affected ones>
 
Do this for SYS first. Shutdown abort and startup and repeat for others.... YMMV!
 
--
John Kanagaraj <><
DB Soft Inc
Phone: 408-970-7002 (W)

Disappointment is always inevitable; Discouragement is invariably optional

** The opinions and facts contained in this message are entirely mine and do not reflect those of my employer or customers **