.ora-code.com

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

Applying redo - recovery fundamentals

2005-11-27       - By Mark Bole
Reply:     1     2     3     4     5     6     7     8     9     10  

orcl wrote:
> All, Im having big  trouble  in a recovery scenario, here is what I have
>
> 1, A small shell of a database with  all datafiles copied to a backup
> location  (cold backup)
> 2. Database is in archivelog mode
> 3. startup up the database and create a table with 6K records.  I can
> see all the redo getting generated wait a few min and drop the table .
> redo logs are 5mb
> 4. Shutdown the database, delete all datafiles and copy over all
> database files  (from step 1)  including redo logs
> 5. Startup mount and issue recover database until cancel
> 6.  I *dont * get prompted for cancel and in 2 seconds i get "media
> recovery complete" and my table *is not* restored
>
> Basically the same problem if I use  recover database until time
> '2005-11-27:09:25:00';
>
> What the heck am I doing wrong?
>
[...]

You need to either restore your current controlfile (not the one you
previously backed up), or create a new one based on the contents of
"backup controfile to trace".  If you simply restore a closed consistent
whole database backup, the instance will correctly determine that no
recovery is needed.

Also, it's not clear in step 4 whether you are referring to archived
redo logs or online redo logs.  It is strongly recommended (by Oracle)
to never backup (or restore) online redo logs.

I personally find that practice with manual recovery is a good thing,
but you can also use RMAN to handle many of the details for you.

--
Mark Bole
http://www.bincomputing.com



--
http://www.freelists.org/webpage/oracle-l