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: Recovery Issues :)

Bobak, Mark

2006-05-11

Replies:
Hi Paula,
 
Ok, it sounds like you've successfully recovered.  Now, the problem w/ the "missing" rows.  This may be where NOLOGGING is relevant.  How is this data loaded?  If it was done as INSERT /*+ APPEND */, then the problem is that, with nologging set, the data was not in the archive logs you applied, so, the segment will need to be truncated and reloaded.  Ideally, the table is partitioned (is it?) so that you can truncate and re-load just that partition.  Right now, if you do a full table scan of the segment, your query will eventually hit the logically corrupt blocks and raise an ORA-26040.  The only way to get rid of those corrupt blocks is to either drop or truncate the segment containing them.
 
For more info on direct load, nologging, and recovery implications, see:  http://dizwell.com/main/index.php?option=com_jd-wiki&Itemid=138&id=directpathoperations
 
Hope that helps,
 
-Mark
 

--
Mark J. Bobak
Senior Oracle Architect
ProQuest Information & Learning

For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled.  --Richard P. Feynman, 1918-1988

 


From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of Paula Stankus
Sent: Thursday, May 11, 2006 11:59 AM
To: Christo Kutrovsky
Cc: Oracle-L@freelists.org
Subject: Re:Recovery Issues :)

Okay,
 
We used the following syntax to recover a database
 
ALTER DATABASE RECOVER DATABASE UNTIL TIME '2006-05-10:09:00:00' USING BACKUP CONTROLFILE
 
Some of the archive files said "no longer needed for recovery"
 
Now, we are told there are rows missing from the night of the 9th (i.e. the night before). 
 
Help :)!


New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.