Watch, Follow, &
Connect with Us

Please visit our new home

Public Report
Report From: InterBase/Server    [ Add a report in this area ]  
Report #:  7952   Status: Closed
Cannot delete external file after external table is dropped
Project:  InterBase Build #:
Version:    8.0 Submitted By:   Bill Todd
Report Type:  Minor failure / Design problem Date Reported:  4/20/2004 12:41:29 PM
Severity:    Infrequently encountered problem Last Updated: 4/26/2013 9:01:27 PM
Platform:    All platforms Internal Tracking #:  
Resolution: Fixed (Resolution Comments) Resolved in Build: : XE3
Duplicate of:  None
Voting and Rating
Overall Rating: (1 Total Rating)
3.00 out of 5
Total Votes: 9
It is not possible to delete the file associated with an external table without first disconnecting all users. This makes reuse of an external table for routine data export difficult or impossible.

While it is possible to drop the external table using DROP TABLE, this does not close the external file and it still cannot be deleted.

Better still, provide a way to close the external table without having to drop and recreate it.

Note: The original report also contained an enhancement request to add support for "DELETE FROM external_table"; that is now oved off to QC 106799 so the issues can be addressed independently.
Steps to Reproduce:
1. Create a database and define an external table
2. Run a query to use the external table
3. DROP TABLE external_table; (and commit if necessary)
4. Keep your database session alive
5. Use any file system explorer and try to delete the file used by the external TABLE

You will notice that the file is reported to be still in use.

abed jbr at 5/28/2012 2:09:48 AM -
  Does this issue was fixed?

At our organization we using Interbase 7 and we dealing with same problem.

At issue report was written Resolved in Build: :
But issue status still Open.

Does it was fixed, and how can we run the fix at our systems.

Also does there any workaround to delete external file after dropping its table?

Kind Regards,

Tomohiro Takahashi at 5/28/2012 6:00:24 AM -
>   Does this issue was fixed?
I will check the internal status of this report.

and, if you need more internsive support and official reply from Embarcadero, please contact technical support service. Sorry for the inconvenience.

Tomohiro Takahashi at 5/28/2012 5:07:19 PM -
This issue is still Open as 'Request for Enhancement'.

Sriram Balasubramanian at 6/30/2012 11:01:43 AM -
This is now entered in our internal BTS as INTB-1462 and will be addressed in an upcoming release

Tomohiro Takahashi at 6/30/2012 6:44:19 PM -
This report was opened.
But, Internal Tracking Number field is still blank.

Server Response from: ETNACODE01