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: Applying redo - recovery fundamentals

Mark W. Farnham


Slight quibble.

As the first step of restore, if you preserve the CURRENT online redo logs
(perhaps in a directory called "try_again") and something goes very wrong in
the recovery that includes pollution of the online redo logs, then you will
be able to try again. I agree that you should not restore something over the
top of the CURRENT online redo logs from backup tapes or online backups that
is older than the CURRENT online redo logs unless a cold previous version of
your database is what you intend to produce.

This handles the case, for example, where you typed in a time a little to
near the present in your "recover until" statement or failed to cancel soon
enough and proceed through "open resetlogs." As you curse yourself for
making the mistake, at least you will be able to try again.


Rightsizing, Inc.
Mark W. Farnham
36 West Street
Lebanon, NH 03766-1239
tel: (603) 448-1803

-----Original Message-----
From: oracle-l-bounce@(protected)
Sent: Sunday, November 27, 2005 9:42 PM
Cc: oracle-l
Subject: Re: Applying redo - recovery fundamentals

NEW pop.tiscali.de wrote:

>You shouldn't be copying the online redo logs in any case, backup or
>restore. You only need to backup archived redo logs.
>Try step 4 without copying back the online redo logs.

OK, I see the error. I was copying the online redo logs AND control
files. The only files needed were the *.dbf Shoudl have
known/researched that.

Recovery worked perfectly



ORA-00279: change 4157085 generated at 11/27/2005 21:31:00 needed for
thread 1
ORA-00289: suggestion : J:\ARCHIVE_DEST\ORCL\ORCL_1_69_575366883.ARC
ORA-00280: change 4157085 for thread 1 is in sequence #69
ORA-00278: log file 'J:\ARCHIVE_DEST\ORCL\ORCL_1_68_575366883.ARC' no
longer needed for this recov

Log applied.
Media recovery complete.
> alter database open resetlogs;

Database altered.

> select count(*) from bitmap_count;