Bobcares

Error dropping database errno: 39 – How we figured it out?

by | Sep 12, 2019

At times, dropping and restoring databases can be a quick way to restore websites.

But, what if database drop attempt ends up in error dropping database errno: 39?

Quite frustrating right?

This error code means that the directory you are trying to drop is not empty, it contains some hidden files.

At Bobcares, we often get requests on database errors as a part of our Server Management Services.

Today, let’s have a look into errno: 39 error code and see how our Support Engineers fix it for our customers.

 

What is error dropping database errno 39?

Database users usually cross many situations where they CREATE, DROP, SELECT databases. Here, let’s look into the DROP DATABASE statement in detail.

For instance, dropping a database means deleting an existing database. So, when does the error errno:39 occur?

One of our customers wanted to drop the database userdb. After executing the command to drop the database, it ended up as,

mysql> drop database userdb;

ERROR 1010 (HY000): Error dropping database (can't rmdir './userdb', errno: 39)

 

Here, the code errno: 39 denotes that the directory is not empty. That is, there are some hidden files in the database directory. But the MySQL is unaware of those files.

Above all, the error statement describes that the MySQL service cannot remove the directory of the database userdb.

A similar error in PHPMyAdmin will appear as :

Fixing errno 39 error

So far, we saw what is errno 39 error while dropping the database.

Now, let’s see how our Support Team fix this error for our customers.

Firstly, we check the database directory. In a Linux system, the database directory location will be usually at /var/lib/mysql

cd /var/lib/mysql/userdb

We list all files in the directory and check for files that show up errors while dropping the database.

Mostly, hidden files, .ibd file, causes the error errno:39.

To fix the error the Support Team removes the error causing files manually.

Database changes are irreversible. Therefore, we always take a backup of the entire database directory to avoid any mishap.

Finally, we execute the DATABASE DROP command. This easily empty the database.

 

[Having difficulty in fixing error dropping database errno 39We will fix it for you.]

 

Conclusion

In short, the error dropping database errno: 39 occurs due to files that are inaccessible by the database. We also saw how our Support Team fix it for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF