Can't securely delete an old database file

[Rick O'Shey]

I was cleaning out a bunch of old files, including an old Entourage Identity
(which had been saved during a rebuild). I wanted to empty the trash
securely, but found that it would stall/hang. I couldn't stop the
trash-emptying process (so that I could open the Trash), unless I relaunched
the Finder.

I deleted the contents of the Trash one-by-one, and discovered that the
database file was the culprit.

Any ideas why? Any suggestions?


(BTW: I'm running 10.5.7)

 

[Kerry]

I was cleaning out a bunch of old files, including an old Entourage Identity
(which had been saved during a rebuild). I wanted to empty the trash
securely, but found that it would stall/hang. I couldn't stop the
trash-emptying process (so that I could open the Trash), unless I relaunched
the Finder.

I deleted the contents of the Trash one-by-one, and discovered that the
database file was the culprit.

Any ideas why? Any suggestions?


(BTW: I'm running 10.5.7)

Reboot or just use secure empty trash from the Apple drop down menu.

 

[Rick O'Shey]

(e-mail address removed), Kerry at

Reboot or just use secure empty trash from the Apple drop down menu.

As I explained, I had been trying to empty the trash securely. And I did
try it via the Trash icon as well as via the Finder menu and the keyboard
(Shift-Cmd-Delete).

The only way I was finally able to delete it was by opening it with BBEdit
(nothing else would open it -- even Word didn't like it, and it was way too
large for something like TextEdit to even attempt) and trying to delete its
contents. I say "trying" because there didn't appear to be any text within
the file, save for a single dashed line (-----------) across the top.
However, after hitting Cmd-A and then Delete, and then tossing it in the
Trash, I was able to successfully securely delete it.

I'd like to understand what it is about this file caused such behavior.

 

[Rick O'Shey]

As I explained, I had been trying to empty the trash securely. And I did
try it via the Trash icon ...

To clarify: I have selected "Empty Trash securely" in my Finder prefs.

 

[William Smith [MVP]]

To clarify: I have selected "Empty Trash securely" in my Finder prefs.

The problem occurs because the Microsoft Database Daemon is still
running and still has the Database file open. Restarting (or logging in
and out) should break the connection. You can also look for the daemon
in /Applications/Utilities/Activity Monitor.app and quit it there. This
should allow you to empty the trash.

Hope this helps!

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[Rick O'Shey]

The problem occurs because the Microsoft Database Daemon is still
running and still has the Database file open. Restarting (or logging in
and out) should break the connection. You can also look for the daemon
in /Applications/Utilities/Activity Monitor.app and quit it there. This
should allow you to empty the trash.

As I indicated, I finally was able to empty the Trash by first retrieving
the file from the Trash; opening it; attempting to delete its contents
(though its contents really didn't show up); saving it; and then sending it
to the Trash again.

As far as the Microsoft Database Daemon having the file open, I don't
understand:

1. Does the daemon, on its own, open a database file that has not been used
for several months?

2. If indeed it _somehow_ does, wouldn't I be aware of it?

3. Would I be able to open it with BBEdit if it were already opened by the
daemon?

 

[Diane Ross]

3. Would I be able to open it with BBEdit if it were already opened by the
daemon?

There is a limit to the size of file BBEdit will open. You'll get error -116
if the file is too big. I know, I tried to open a database last night that
was a tad over 2GB and got this error.

 

[Rick O'Shey]

There is a limit to the size of file BBEdit will open. You'll get error -116
if the file is too big. I know, I tried to open a database last night that
was a tad over 2GB and got this error.

The file was about 4 GB (part of an old Identity that was saved during a
database rebuild). It couldn't be deleted (trash-emptying would stall/hang
-- I'd have to relaunch the Finder). Regarding BBEdit, as I explained in the
second post in this thread:

"The only way I was finally able to delete it was by opening it with BBEdit
(nothing else would open it -- even Word didn't like it, and it was way too
large for something like TextEdit to even attempt) and trying to delete its
contents. I say "trying" because there didn't appear to be any text within
the file, save for a single dashed line (-----------) across the top.
However, after hitting Cmd-A and then Delete, and then tossing it in the
Trash, I was able to successfully securely delete it.

I'd like to understand what it is about this file caused such behavior."

 

[Diane Ross]

I'd like to understand what it is about this file caused such behavior."

Probably something corrupted that the Finder didn't like.


Did you try the File > hold down Option key select Empty Trash?

 

[Rick O'Shey]

Probably something corrupted that the Finder didn't like.

A "Finder Fluke."

Did you try the File > hold down Option key select Empty Trash?

Yes I did.

Oh well...as long as it was only a "Finder Fluke" and not a "Finder Goblin."

 

[Diane Ross]

Oh well...as long as it was only a "Finder Fluke" and not a "Finder Goblin."

That only happens on Halloween.

 

[Rick O'Shey]

That only happens on Halloween.

<rim shot!>