Accident may happens, even though it’s costly one. This is especially the case in Oracle database,
which stores the database objects physically in data files on hard
disk. Fast hand administrators may accidentally delete some of the
datafiles, or the datafiles may get corrupted or unreadable on hard disk
failure. You may get also some missing datafiles after database recovery
process. In any case, missing a or a few datafiles will cause Oracle
database to fail to startup, rendering the whole DB inaccessible.
The solution to the missing datafiles is to drop the affected tablespace where has incomplete datafiles, and then recreate the tablespace and import the data into the tablespace from backup. However, the steps are not so straight forward.
The solution to the missing datafiles is to drop the affected tablespace where has incomplete datafiles, and then recreate the tablespace and import the data into the tablespace from backup. However, the steps are not so straight forward.
- Run SQL*Plus.
- Connect to database as SYSDBA with this query:
CONNECT / AS SYSDBA
- Mount the database instead of starting it up:
STARTUP MOUNT;
- Issue the following command to bring the missing datafile offline so that Oracle won’t trying to connect and access the datafile anymore:
ALTER DATABASE DATAFILE ‘
’ OFFLINE DROP;
Repeat the command for every datafiles that unaccounted for. - Now start the database proper:
ALTER DATABASE OPEN;
- As the tablespace has damaged, drop it to recreate from fresh backup.
DROP TABLESPACE
INCLUDING CONTENTS;
- Ensure the other datafiles for the tablespace has been deleted, if not, remove them manually from the operating system. Tip: How to check datafiles that belong to tablespace.
- Continue with the recovery process.
No comments:
Post a Comment