Database Reference
In-Depth Information
exeRCiSe 2.2
(continued)
ORA-00289: suggestion :
/oracle01/fast_recovery_area/ORCL/archivelog
/2013_08_17/o1_mf_1_9_4bk9p2mz_.arcORA-00280:
change 5112647 for thread 1 is in sequence #9
Log applied.
Media recovery complete.
8.
Oracle will apply the needed redo and then return you to the SQL prompt. Assuming no
errors occur, you can now open the database with the
ALTER DATABASE OPEN
command,
as shown here:
SQL> alter database open;
Database altered.
Recovering the Database after the Loss of the SYSTEM or
UNDO Tablespace Data File
In this case, we will just restore the tablespaces or data files that were lost. Of course,
because these are critical tablespace objects, the database itself is down. After restoring the
data files that were lost (do not restore any data files that are intact), recover the database
following these steps:
1.
Log into the database as
SYS
using
SYSDBA
authentication.
2.
Mount the database with the
STARTUP MOUNT
command.
For recovery, you have two options. You can use the
RECOVER TABLESPACE
or the
RECOVER
DATAFILE
command to recover the data files that were lost. It's kind of up to you which
one you want to use (we like the
RECOVER TABLESPACE
command in this situation more
because it's easier to do since it covers all the data files). The various recover commands
(
RECOVER DATABASE
,
RECOVER TABLESPACE
, and
RECOVER DATAFILE)
will recommend the
correct archived redo log to apply.
3.
At the prompt, type
AUTO
.
The
RECOVER DATABASE
command (as well as
RECOVER TABLESPACE
or
RECOVER
DATAFILE
) automatically starts applying all redo until the database is recovered.
4.
Once database recovery is complete, the
RECOVER DATABASE
command will return you
to the SQL prompt. You can then issue the
ALTER DATABASE OPEN
command to open
the database for business.
Search WWH ::
Custom Search