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: urgent recovery question

Mark Brinsmead

2006-05-11

Replies:
Backing up immediately after a NOLOGGING operation may well be your best bet.  (Aside, perhaps, from not doing nologging operations in the first place.)  But the backup need not be a FULL backup; an incremental is just as good.  Or, at least, so say the doc's.



On 5/11/06, Paula Stankus <paulastankus@yahoo.com> wrote:
We had a database with some tablespaces marked as nologging
 
Sys admin. copied files from backup on top of those files (hot backup)
 
Tablespaces with "nologging" complianed about needing media recovery.
 
Is the only way to circumvent this problem be to backup immediately after loads? 
 
Question:  Would flash recovery assist in recovery when datafiles are deleted or corrupted?


How low will we go? Check out Yahoo! Messenger's low PC-to-Phone call rates.





--
Cheers,
-- Mark Brinsmead
   Staff DBA,
   The Pythian Group
   http://www.pythian.com/blogs