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 question

Bobak, Mark


Hi Joe,

Two things:

1.) If the controlfile was restored, then do: recover database until
time '2006-05-10:09:15:00' using backup controlfile;
2.) Make sure you resetlogs for a point-in-time recovery: alter
database open resetlogs;

I think that will get him where he wants to be.

To answer your questions:
1.) Yes.
2.) Yes.
3.) Exactly, which is why I said to use 'using backup controlfile'

Hope that helps,


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

-----Original Message-----
From: oracle-l-bounce@(protected)
Sent: Wednesday, May 10, 2006 4:17 PM
To: Oracle-L@(protected)
Subject: recovery question

In the middle of researching for a colleague, but thought I'd check here

OS HP-UX B11.00

Wanted to restore database to 9:15am server time this morning (5/10/06).
Last hot backup was (5/7/06). All database files and controlfiles were
restored and then he did this:


> sqlplus

SQL*Plus: Release - Production on Wed May 10 12:37:58 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Enter user-name: sys as sysdba
Enter password:
Connected to an idle instance.

SQL> startup mount
ORACLE instance started.
Total System Global Area 162525384 bytes
Fixed Size             737480 bytes
Variable Size         109051904 bytes
Database Buffers       52428800 bytes
Redo Buffers           307200 bytes
Database mounted.

SQL> Recover database until time '2006-05-10:09:15:00';
Media recovery complete.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open noresetlogs;
Database altered.


Customer said they did not see changes after 5/7. I had my guy run the
following query to check on the archive logs timestamps:

select to_char(first_time, 'DD-MON-YYYY HH:MI:SS') from v$loghist;

and the last few lines returned were:

04-MAY-2006 11:07:37
04-MAY-2006 11:08:24
05-MAY-2006 07:41:00
06-MAY-2006 10:01:17
07-MAY-2006 12:00:26
07-MAY-2006 03:00:09

It seems that the database was not rolled forward to the time he wanted.
And, of course, a new archive log has over-written the old archive log
because the database was opened noresetlogs and blah, blah, blah.

He has all the old archive logs and is now restoring the Sunday backup
again for attempt #2 and I am trying to help make this one successful.

1. Should he see the archive logs being applied as it occurs? (I would
think yes) 2. Should he open resetlogs to avoid any archive/redo issues
when opening the database in the future? (Again, I lean towards yes
given what just happened to him :-) ) 3. It seems to me the real
problem is that he restored the Sunday controlfile which only know about
archive logs up to the time the backup was taken. Therefore, the
recover command completed almost immediately without applying logs
because there were no logs to apply. Soo, does he recreate the
controlfile and then issue the same command plus "using backup
controlfile"? Any other suggestions?