Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On an Oracle 11.2g DB; We have a corrupted TS that does not allow starting the database instance above mount state. The TS cannot be removed with standard methods (i.e., enterprise manager).

What can we do?
What other information is needed to diagnose the problem?

(We've meanwhile checked the file system, which is ok, but the DBF file for the tablespace is lost.)

share|improve this question
up vote 4 down vote accepted

If you just want to remove the tablespace have you tried logging in as sys and dropping it?

DROP TABLESPACE <tablespace>

If so, what error message do you receive? (I'm assuming you've made a cold backup of the database at this point in case the tablespace is needed.)

Alternatively, if you can determine which datafile is corrupt you can remove this from the tablespace:


Make sure that <filename> is the filename known to Oracle, especially if any links may be involved on disk! Otherwise you will get misleading errors about non-existent files.

share|improve this answer
The former command results in ORA-01109: database not open. The second command results in ORA-01516: nonexistent log file, data file, or temporary file although the file does exist, is readable (although it doesn't contain correct data). – stmoebius Feb 9 '12 at 12:59
Never mind. There was a path mismatch, or, put differently, we were trying to delete a file which existed, but was not registered with the DB. – stmoebius Feb 9 '12 at 13:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.