Skip to content
JackSparrow414
Go back

Problems Caused by Deleting Oracle Tablespace Files Directly

Table of contents

Open Table of contents

Article body

The situation: while importing into Oracle today, I was told that tablespace A already existed. Based on a previous painful experience, I stopped the Oracle components and deleted the file directly from its folder with a right-click. I thought this should be fine, provided everything in Oracle was stopped before deleting it this way. This time, however, it immediately caused ORA-01109: database not open. That began a long troubleshooting session.

Here is a solution for database not open; I tried it myself and it worked.

However, the second step produced ORA-12514. The specific solution is described inORA-12514。

After that, I returned to the original procedure and finally resolved the issue. It cost me two hours.

To recap: 1. I started by deleting the tablespace file directly. I should have followed the normal procedure: drop tablespace TABLESPACE_NAME Including…

                  2. This caused the database-not-open error, ORA-01109.

                 3. A TNS listener problem appeared when logging in as SYSDBA. Restarting it did not help, but reconfiguring the listener resolved it.

                 4. ORA-12514 appeared during troubleshooting and was resolved.

                5. The tablespace was finally deleted successfully, and the problem was resolved.


Share this post:

Previous Post
Useful Blog Posts about Network Frames
Next Post
Oracle Window Functions

Comments

Questions, corrections, and experiences are welcome. Sign in with GitHub to comment; both language versions share this discussion.

Comments are available on the live site only.